From: "John (Eljay) Love-Jensen" <eljay@adobe.com>
To: "Thomas Mittelstaedt" <T.Mittelstaedt@cadenas.de>,
<gcc-help@gcc.gnu.org>
Subject: RE: Problem building gcc-4.2.2 on 64-bit ubuntu linux
Date: Wed, 19 Dec 2007 12:36:00 -0000 [thread overview]
Message-ID: <EDC8DDD212FEB34C884CBB0EE8EC2D91081F68F3@namailgen.corp.adobe.com> (raw)
In-Reply-To: <4768E104.2000801@cadenas.de>
Hi Thomas,
>../configure --prefix=/opt/gcc-4.2.2
--enable-version-specific-runtime-libs --enable-static --enable-shared
--enable-languages=c,c++,java,objc,obj-c++ --enable-threads=posix
--enable-nls --enable-__cxa_atexit --enable-libstdcxx-debug
--enable-checking=release x86_64-linux-gnu
It appears that you are attempting to build GCC from within a subdirectory of the GCC source code (instead of, say, a peer directory to the GCC source code).
Since that situation is not supported as per <http://gcc.gnu.org/install/configure.html>, do you get the same problem if you build to a peer directory to the source code?
Note: the source code tree may be "tainted" and could need to be "rm -rf" and "tar -x" afresh.
I do not know if this is related to the problem encountered or not. Just one of the variables to consider taking out of the equation.
Sincerely,
--Eljay
next prev parent reply other threads:[~2007-12-19 12:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 9:09 Thomas Mittelstaedt
2007-12-19 12:36 ` John (Eljay) Love-Jensen [this message]
2007-12-19 13:34 ` Thomas Mittelstaedt
2007-12-19 14:32 ` Thomas Mittelstaedt
2007-12-19 15:00 ` Kai Ruottu
2007-12-19 15:14 ` Kai Ruottu
2007-12-19 15:03 ` Thomas Mittelstaedt
2007-12-19 16:55 ` Thomas Mittelstaedt
2007-12-20 1:56 ` Tim Prince
2007-12-20 6:17 ` Brian Dessent
2007-12-20 13:33 ` Problem building gcc-4.2.2 on 64-bit ubuntu linux, SUCCESS!! Thomas Mittelstaedt
2007-12-20 7:21 ` Problem building gcc-4.2.2 on 64-bit ubuntu linux Fabian Cenedese
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=EDC8DDD212FEB34C884CBB0EE8EC2D91081F68F3@namailgen.corp.adobe.com \
--to=eljay@adobe.com \
--cc=T.Mittelstaedt@cadenas.de \
--cc=gcc-help@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: link
Be 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).