From: Thomas Mittelstaedt <T.Mittelstaedt@cadenas.de>
To: gcc-help@gcc.gnu.org
Subject: Re: Problem building gcc-4.2.2 on 64-bit ubuntu linux
Date: Wed, 19 Dec 2007 14:32:00 -0000 [thread overview]
Message-ID: <47692CD3.7040708@cadenas.de> (raw)
In-Reply-To: <47691F4A.4010607@cadenas.de>
Okay, restartet from scratch with the following, but the
I/usr/include/i486-linux-gnu/ would still not propagate.
../gcc-4.2.2/configure --prefix=/opt/gcc-4.2.2
--enable-version-specific-runtime-libs --enable-static --enable-shared
--enable-languages=c,c++,objc,obj-c++ --enable-threads=posix
--enable-nls --enable-__cxa_atexit --enable-libstdcxx-debug
--enable-checking=release
make CFLAGS_FOR_TARGET="-I/usr/include/i486-linux-gnu/" CFLAGS='-O'
LIBCFLAGS='-g -O2' LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap
/localbuild/gcc-build/./gcc/xgcc -shared-libgcc
-B/localbuild/gcc-build/./gcc -nostdinc++
-L/localbuild/gcc-build/x86_64-unknown-linux-gnu/32/libstdc++-v3/src
-L/localbuild/gcc-build/x86_64-unknown-linux-gnu/32/libstdc++-v3/src/.libs
-B/opt/gcc-4.2.2/x86_64-unknown-linux-gnu/bin/
-B/opt/gcc-4.2.2/x86_64-unknown-linux-gnu/lib/ -isystem
/opt/gcc-4.2.2/x86_64-unknown-linux-gnu/include -isystem
/opt/gcc-4.2.2/x86_64-unknown-linux-gnu/sys-include -m32
-I/localbuild/gcc-4.2.2/libstdc++-v3/../gcc
-I/localbuild/gcc-build/x86_64-unknown-linux-gnu/32/libstdc++-v3/include/x86_64-unknown-linux-gnu
-I/localbuild/gcc-build/x86_64-unknown-linux-gnu/32/libstdc++-v3/include
-I/localbuild/gcc-4.2.2/libstdc++-v3/libsupc++ -fno-implicit-templates
-Wall -Wextra -Wwrite-strings -Wcast-qual
-fdiagnostics-show-location=once -ffunction-sections -fdata-sections -g
-O2 -D_GNU_SOURCE -m32 -c
../../../../../gcc-4.2.2/libstdc++-v3/libsupc++/del_op.cc -fPIC -DPIC
-o del_op.o
In file included from /usr/include/features.h:346,
from
/localbuild/gcc-build/x86_64-unknown-linux-gnu/32/libstdc++-v3/include/x86_64-unknown-linux-gnu/bits/os_defines.h:44,
from
/localbuild/gcc-build/x86_64-unknown-linux-gnu/32/libstdc++-v3/include/x86_64-unknown-linux-gnu/bits/c++config.h:41,
from
../../../../../gcc-4.2.2/libstdc++-v3/libsupc++/del_op.cc:31:
/usr/include/gnu/stubs.h:7:27: error: gnu/stubs-32.h: No such file or
directory
make[8]: *** [del_op.lo] Error 1
make[8]: Leaving directory
`/localbuild/gcc-build/x86_64-unknown-linux-gnu/32/libstdc++-v3/libsupc++'
Thomas Mittelstaedt schrieb:
>
> John (Eljay) Love-Jensen schrieb:
>
>> 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).
>>
>>
>>
> Oh, man. me *bummer*. I did read the configure page, but not thoroughly
> enough (maybe too fast). :-[
> I'll redo it cleanly!
>
>
>> 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 14:32 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
2007-12-19 13:34 ` Thomas Mittelstaedt
2007-12-19 14:32 ` Thomas Mittelstaedt [this message]
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=47692CD3.7040708@cadenas.de \
--to=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).