public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: reichelt@igpm.rwth-aachen.de To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, hfanous@rogers.com, nobody@gcc.gnu.org Subject: Re: other/8283: Failed to build native GCC-3.2 on i686 linux machine Date: Fri, 08 Nov 2002 14:18:00 -0000 [thread overview] Message-ID: <20021108221839.18806.qmail@sources.redhat.com> (raw) Synopsis: Failed to build native GCC-3.2 on i686 linux machine State-Changed-From-To: open->feedback State-Changed-By: reichelt State-Changed-When: Fri Nov 8 14:18:39 2002 State-Changed-Why: Maybe your problems arise from a faulty configuration. http://gcc.gnu.org/install/configure.html says: First, we highly recommend that GCC be built into a separate directory than the sources which does not reside within the source tree. This is how we generally build GCC; building where srcdir == objdir should still work, but doesn't get extensive testing; building where objdir is a subdirectory of srcdir is unsupported. You are trying to build in "obj" which you created as a subdirectory of the srcdir gcc-3.2. You should try to configure the compiler as follows: tar zxf gcc-3.2.tar.gz mkdir obj cd obj ../gcc-3.2/configure --program-suffix=-3.2 --enable-shared --with-gnu-as --with-gnu-ld --enable-threads=posix --enable-version-specific-runtime-libs make bootstrap Please tell us, whether this solves your build problems or not. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8283
next reply other threads:[~2002-11-08 22:18 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-08 14:18 reichelt [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-23 21:14 neroden 2002-10-19 5:06 hfanous
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20021108221839.18806.qmail@sources.redhat.com \ --to=reichelt@igpm.rwth-aachen.de \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=hfanous@rogers.com \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).