* Problem building gcc-4.2.2 on 64-bit ubuntu linux
@ 2007-12-19 9:09 Thomas Mittelstaedt
2007-12-19 12:36 ` John (Eljay) Love-Jensen
0 siblings, 1 reply; 12+ messages in thread
From: Thomas Mittelstaedt @ 2007-12-19 9:09 UTC (permalink / raw)
To: gcc-help
Hi, everyone,
I'm trying to build gcc on a 64-bit linux and
am getting error in stage2 (=stage_current:
Must remake target `java/parse-scan.o'.
/localbuild/gcc-4.2.2/.obj/./prev-gcc/xgcc
-B/localbuild/gcc-4.2.2/.obj/./prev-gcc/
-B/opt/gcc-4.2.2/x86_64-linux-gnu/bin/ -c -g -O2 -DIN_GCC -W -Wall
-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic
-Wno-long-long -Wno-variadic-macros -Wno-overlength-strings
-Wold-style-definition -Wmissing-format-attribute -Wno-error
-DHAVE_CONFIG_H -I. -Ijava -I../../gcc -I../../gcc/java
-I../../gcc/../include -I../../gcc/../libcpp/include
-I../../gcc/../libdecnumber -I../libdecnumber java/parse-scan.c -o
java/parse-scan.o
In file included from ../../gcc/java/lex.c:37,
from ../../gcc/java/parse-scan.y:136:
../../gcc/java/keyword.h: In function 'java_keyword':
../../gcc/java/keyword.h:110: error: 'ELSE_TK' undeclared (first use in
this function)
../../gcc/java/keyword.h:110: error: (Each undeclared identifier is
reported only once
../../gcc/java/keyword.h:110: error: for each function it appears in.)
../../gcc/java/keyword.h:110: warning: missing initializer
....
I configured with:
../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
and built with:
make --debug=b CFLAGS_FOR_TARGET="-I/usr/include/i486-linux-gnu/"
CFLAGS='-O' LIBCFLAGS='-g -O2' LIBCXXFLAGS='-g -O2
-fno-implicit-templates' bootstrap
uname -a:
Linux buildlnx2 2.6.17-10-generic #2 SMP Fri Oct 13 15:34:39 UTC 2006
x86_64 GNU/Linux
thomas
^ permalink raw reply [flat|nested] 12+ messages in thread* RE: Problem building gcc-4.2.2 on 64-bit ubuntu linux 2007-12-19 9:09 Problem building gcc-4.2.2 on 64-bit ubuntu linux Thomas Mittelstaedt @ 2007-12-19 12:36 ` John (Eljay) Love-Jensen 2007-12-19 13:34 ` Thomas Mittelstaedt 0 siblings, 1 reply; 12+ messages in thread From: John (Eljay) Love-Jensen @ 2007-12-19 12:36 UTC (permalink / raw) To: Thomas Mittelstaedt, gcc-help 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 ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Problem building gcc-4.2.2 on 64-bit ubuntu linux 2007-12-19 12:36 ` John (Eljay) Love-Jensen @ 2007-12-19 13:34 ` Thomas Mittelstaedt 2007-12-19 14:32 ` Thomas Mittelstaedt 0 siblings, 1 reply; 12+ messages in thread From: Thomas Mittelstaedt @ 2007-12-19 13:34 UTC (permalink / raw) To: John (Eljay) Love-Jensen; +Cc: gcc-help 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 > ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Problem building gcc-4.2.2 on 64-bit ubuntu linux 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:03 ` Thomas Mittelstaedt 0 siblings, 2 replies; 12+ messages in thread From: Thomas Mittelstaedt @ 2007-12-19 14:32 UTC (permalink / raw) To: gcc-help 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 >> >> ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Problem building gcc-4.2.2 on 64-bit ubuntu linux 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 1 sibling, 1 reply; 12+ messages in thread From: Kai Ruottu @ 2007-12-19 15:00 UTC (permalink / raw) To: Thomas Mittelstaedt; +Cc: gcc-help Thomas Mittelstaedt wrote: > Okay, restartet from scratch with the following, but the I/usr/include/i486-linux-gnu/ would still not propagate. A 64-bit Linux should have its bi-arch (for 64- and 32-bit) native headers in fully usual '/usr/include'. So your '-I' should be totally vain.... > /usr/include/gnu/stubs.h:7:27: error: gnu/stubs-32.h: No such file or directory This should come with the optional 32-bit development headers & libraries, in an install package like: ftp://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive/pool/main/g/glibc/libc6-dev-i386_2.7-4ubuntu1_amd64.deb Just check what your installed glibc version is and then try to find the missing component for it. Maybe there is some simple "package installer" in Ubuntu, letting you to choose something like "32-bit development libraries" to be installed. ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Problem building gcc-4.2.2 on 64-bit ubuntu linux 2007-12-19 15:00 ` Kai Ruottu @ 2007-12-19 15:14 ` Kai Ruottu 0 siblings, 0 replies; 12+ messages in thread From: Kai Ruottu @ 2007-12-19 15:14 UTC (permalink / raw) To: Thomas Mittelstaedt; +Cc: gcc-help Kai Ruottu wrote: > Thomas Mittelstaedt wrote: > > > /usr/include/gnu/stubs.h:7:27: error: gnu/stubs-32.h: No such file > or directory > > This should come with the optional 32-bit development headers & > libraries, in an install package like: > > ftp://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive/pool/main/g/glibc/libc6-dev-i386_2.7-4ubuntu1_amd64.deb > I checked my Ubuntu 7.04 Desktop AMD64 Install CD and it had ONLY the 64-bit development package! Maybe Ubuntu provides an install DVD with "everything" belonging to the distro but at least this CD was a little "restricted". Maybe the rest would be installed from the net after installing the base system from this CD... ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Problem building gcc-4.2.2 on 64-bit ubuntu linux 2007-12-19 14:32 ` Thomas Mittelstaedt 2007-12-19 15:00 ` Kai Ruottu @ 2007-12-19 15:03 ` Thomas Mittelstaedt 2007-12-19 16:55 ` Thomas Mittelstaedt 1 sibling, 1 reply; 12+ messages in thread From: Thomas Mittelstaedt @ 2007-12-19 15:03 UTC (permalink / raw) To: gcc-help Quick & dirty just added it to LTCXXCOMPILE in the generated Makefile's in x86_64-unknown-linux-gnu/32/libstdc++-v3/ and below LTCXXCOMPILE = $(LIBTOOL) --tag CXX --tag disable-shared \ --mode=compile $(CXX) $(TOPLEVEL_INCLUDES) \ $(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CXXFLAGS) $(CXXFLAGS) \ -I/usr/include/i486-linux-gnu/ and the build would continue until: Running configure in multilib subdirs 32 pwd: /localbuild/gcc-build/x86_64-unknown-linux-gnu/libmudflap Running configure in multilib subdir 32 pwd: /localbuild/gcc-build/x86_64-unknown-linux-gnu configure: loading cache ./config.cache checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking target system type... x86_64-unknown-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for --enable-version-specific-runtime-libs... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for x86_64-unknown-linux-gnu-gcc... /localbuild/gcc-build/./gcc/xgcc -B/localbuild/gcc-build/./gcc/ -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 checking for C compiler default output file name... a.out checking whether the C compiler works... configure: error: cannot run C compiled programs. If you meant to cross compile, use `--host'. See `config.log' for more details. make[1]: *** [configure-target-libmudflap] Error 1 make[1]: Leaving directory `/localbuild/gcc-build' make: *** [bootstrap] Error 2 Thomas Mittelstaedt schrieb: > 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 >>> >>> >>> ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Problem building gcc-4.2.2 on 64-bit ubuntu linux 2007-12-19 15:03 ` Thomas Mittelstaedt @ 2007-12-19 16:55 ` Thomas Mittelstaedt 2007-12-20 1:56 ` Tim Prince 0 siblings, 1 reply; 12+ messages in thread From: Thomas Mittelstaedt @ 2007-12-19 16:55 UTC (permalink / raw) To: gcc-help and x86_64-unknown-linux-gnu/32/libmudflap/config.log says: configure:2308: checking for C compiler default output file name configure:2311: /localbuild/gcc-build/./gcc/xgcc -B/localbuild/gcc-build/./gcc/ -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/usr/include/i486-linux-gnu/ conftest.c >&5 /usr/bin/ld: skipping incompatible /usr/lib/../lib/libc.so when searching for -lc /usr/bin/ld: skipping incompatible /usr/lib/../lib/libc.a when searching for -lc /usr/bin/ld: skipping incompatible /usr/bin/../lib/libc.so when searching for -lc /usr/bin/ld: skipping incompatible /usr/bin/../lib/libc.a when searching for -lc /usr/bin/ld: warning: i386:x86-64 architecture of input file `/usr/lib/../lib/crt1.o' is incompatible with i386 output /usr/bin/ld: warning: i386:x86-64 architecture of input file `/usr/lib/../lib/crti.o' is incompatible with i386 output /usr/bin/ld: warning: i386:x86-64 architecture of input file `/usr/lib/../lib/crtn.o' is incompatible with i386 output configure:2314: $? = 0 configure:2360: result: a.out configure:2365: checking whether the C compiler works configure:2371: ./a.out Segmentation fault configure:2374: $? = 139 configure:2381: error: cannot run C compiled programs. my installed gcc works with -m32 and produces runnable programs. Thomas Mittelstaedt schrieb: > Quick & dirty just added it to LTCXXCOMPILE in the generated Makefile's in > x86_64-unknown-linux-gnu/32/libstdc++-v3/ and below > > > LTCXXCOMPILE = $(LIBTOOL) --tag CXX --tag disable-shared \ > --mode=compile $(CXX) $(TOPLEVEL_INCLUDES) \ > $(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CXXFLAGS) $(CXXFLAGS) \ > -I/usr/include/i486-linux-gnu/ > > and the build would continue until: > Running configure in multilib subdirs 32 > pwd: /localbuild/gcc-build/x86_64-unknown-linux-gnu/libmudflap > Running configure in multilib subdir 32 > pwd: /localbuild/gcc-build/x86_64-unknown-linux-gnu > configure: loading cache ./config.cache > checking build system type... x86_64-unknown-linux-gnu > checking host system type... x86_64-unknown-linux-gnu > checking target system type... x86_64-unknown-linux-gnu > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for gawk... gawk > checking whether make sets $(MAKE)... yes > checking for --enable-version-specific-runtime-libs... yes > checking whether to enable maintainer-specific portions of Makefiles... no > checking for x86_64-unknown-linux-gnu-gcc... > /localbuild/gcc-build/./gcc/xgcc -B/localbuild/gcc-build/./gcc/ > -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 > checking for C compiler default output file name... a.out > checking whether the C compiler works... configure: error: cannot run C > compiled programs. > If you meant to cross compile, use `--host'. > See `config.log' for more details. > make[1]: *** [configure-target-libmudflap] Error 1 > make[1]: Leaving directory `/localbuild/gcc-build' > make: *** [bootstrap] Error 2 > > > > Thomas Mittelstaedt schrieb: > >> 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 >>>> >>>> >>>> >>>> ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Problem building gcc-4.2.2 on 64-bit ubuntu linux 2007-12-19 16:55 ` Thomas Mittelstaedt @ 2007-12-20 1:56 ` Tim Prince 2007-12-20 6:17 ` Brian Dessent 2007-12-20 7:21 ` Problem building gcc-4.2.2 on 64-bit ubuntu linux Fabian Cenedese 0 siblings, 2 replies; 12+ messages in thread From: Tim Prince @ 2007-12-20 1:56 UTC (permalink / raw) To: Thomas Mittelstaedt; +Cc: gcc-help Thomas Mittelstaedt wrote: > and x86_64-unknown-linux-gnu/32/libmudflap/config.log says: > > configure:2308: checking for C compiler default output file name > configure:2311: /localbuild/gcc-build/./gcc/xgcc > -B/localbuild/gcc-build/./gcc/ > -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/usr/include/i486-linux-gnu/ conftest.c >&5 > /usr/bin/ld: skipping incompatible /usr/lib/../lib/libc.so when > searching for -lc > /usr/bin/ld: skipping incompatible /usr/lib/../lib/libc.a when searching > for -lc > /usr/bin/ld: skipping incompatible /usr/bin/../lib/libc.so when > searching for -lc > /usr/bin/ld: skipping incompatible /usr/bin/../lib/libc.a when searching > for -lc > /usr/bin/ld: warning: i386:x86-64 architecture of input file > `/usr/lib/../lib/crt1.o' is incompatible with i386 output > /usr/bin/ld: warning: i386:x86-64 architecture of input file > `/usr/lib/../lib/crti.o' is incompatible with i386 output > /usr/bin/ld: warning: i386:x86-64 architecture of input file > `/usr/lib/../lib/crtn.o' is incompatible with i386 output Ubuntu decided to find a 64- vs 32- bit setup incompatible with predecessor distros. Presumably, there is an ubuntu patch set for this, but it's quite inconvenient that they chose to break the scheme chosen by their predecessors. The scheme chosen by everyone else is to put the 64-bit stuff in /usr/lib64, and the 32-bit stuff in /usr/lib. Pretty much the kind of mess Bill Gates wanted to see the alternatives get into. ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Problem building gcc-4.2.2 on 64-bit ubuntu linux 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 1 sibling, 1 reply; 12+ messages in thread From: Brian Dessent @ 2007-12-20 6:17 UTC (permalink / raw) To: Tim Prince; +Cc: Thomas Mittelstaedt, gcc-help Tim Prince wrote: > Ubuntu decided to find a 64- vs 32- bit setup incompatible with > predecessor distros. Not just Ubuntu, but Debian (and anything based on Debian.) You make it out to seem like the Debian maintainers did this because they just felt like being different, but I'm sure they had their own good reasons. After all, they had to maintain a local patch in their gcc trees to make it work, so it's not like they didn't also feel the burden of this. If the distro maintainers thought that the tradeoff of making tens of thousands of packages easier for their team of maintainers to manage warrants a two line change in some gcc configury, then that's their right. > Presumably, there is an ubuntu patch set for this, > but it's quite inconvenient that they chose to break the scheme chosen > by their predecessors. The scheme chosen by everyone else is to put the > 64-bit stuff in /usr/lib64, and the 32-bit stuff in /usr/lib. The patch to make this alternative layout work has been in mainline gcc for more than 2 months: <http://gcc.gnu.org/viewcvs?view=rev&revision=128845> so the issue is now moot, or at least it will be before too long. > Pretty > much the kind of mess Bill Gates wanted to see the alternatives get into. And this is relevant how?!? Yes, it sure does suck that you can't install gcc in Debian. Oh wait, you can: "apt-get install gcc". The fact that Debian maintainers go out of their way to modify and "Debianize" many software packages sometimes does mean that occasionally patches are required to get upstream sources to work. This is a feature not a bug, and it's one of the reasons why I happen to cherish Debian based systems above all others. If you want something that's just a bunch of software thrown together without any patches (= without any cohesion), by all means run far and fast from Debian; it will drive you crazy. Brian ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Problem building gcc-4.2.2 on 64-bit ubuntu linux, SUCCESS!! 2007-12-20 6:17 ` Brian Dessent @ 2007-12-20 13:33 ` Thomas Mittelstaedt 0 siblings, 0 replies; 12+ messages in thread From: Thomas Mittelstaedt @ 2007-12-20 13:33 UTC (permalink / raw) To: gcc-help; +Cc: Tim Prince, brian Thank you for the hint, Brian Now it compiles to the finish and works (builds small test program, builds binutils 2.18), but I had to change line 172 in libmudflap/mf-runtime.c from uintptr_t __mf_lc_mask = LOOKUP_CACHE_MASK_DFL; to __mf_uintptr_t __mf_lc_mask = LOOKUP_CACHE_MASK_DFL; so that it corresponds with the decl in the header file, but get lots of warnings now: /bin/sh ./libtool --mode=compile /localbuild/gcc-build/./gcc/xgcc -B/localbuild/gcc-build/./gcc/ -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 -DHAVE_CONFIG_H -I. -I../../../gcc-4.2.2/libmudflap -I. -Wall -ffunction-sections -fdata-sections -I/usr/include/i486-linux-gnu/ -DLIBMUDFLAPTH -c ../../../gcc-4.2.2/libmudflap/mf-hooks2.c -o pth/mf-hooks2.lo /localbuild/gcc-build/./gcc/xgcc -B/localbuild/gcc-build/./gcc/ -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 -DHAVE_CONFIG_H -I. -I../../../gcc-4.2.2/libmudflap -I. -Wall -ffunction-sections -fdata-sections -I/usr/include/i486-linux-gnu/ -DLIBMUDFLAPTH -c ../../../gcc-4.2.2/libmudflap/mf-hooks2.c -fPIC -DPIC -o pth/.libs/mf-hooks2.o ../../../gcc-4.2.2/libmudflap/mf-hooks2.c: In function '__mfwrap_memcpy': ../../../gcc-4.2.2/libmudflap/mf-hooks2.c:137: warning: cast from pointer to integer of different size ../../../gcc-4.2.2/libmudflap/mf-hooks2.c:137: warning: cast from pointer to integer of different size ../../../gcc-4.2.2/libmudflap/mf-hooks2.c:137: warning: cast from pointer to integer of different size ../../../gcc-4.2.2/libmudflap/mf-hooks2.c:137: warning: cast from pointer to integer of different size I also had to adjust files in the installation, since the installed gcc complained about gcc_s.so not been found when linking: tmstaedt@buildlnx2:/opt/gcc-4.2.2$ mv lib32/libiberty.a lib/gcc/x86_64-unknown-linux-gnu/lib lib32/ lib64/ tmstaedt@buildlnx2:/opt/gcc-4.2.2$ mv lib32/libiberty.a lib/gcc/x86_64-unknown-linux-gnu/lib32/ tmstaedt@buildlnx2:/opt/gcc-4.2.2$ mv lib64/libiberty.a lib/gcc/x86_64-unknown-linux-gnu/lib64/ tmstaedt@buildlnx2:/opt/gcc-4.2.2$ pwd /opt/gcc-4.2.2 tmstaedt@buildlnx2:/opt/gcc-4.2.2$ mv lib32/ lib32.bak tmstaedt@buildlnx2:/opt/gcc-4.2.2$ mv lib64/ lib64.bak tmstaedt@buildlnx2:/opt/gcc-4.2.2$ ln -s lib/gcc/x86_64-unknown-linux-gnu/lib32/ lib32 tmstaedt@buildlnx2:/opt/gcc-4.2.2$ ln -s lib/gcc/x86_64-unknown-linux-gnu/lib64/ lib64 =========================== tmstaedt@buildlnx2:/localbuild/gcc-4.2.2/gcc/config/i386$ diff t-linux64.orig t-linux64 6a7,13 > # On Debian, Ubuntu and other derivitive distributions, the 32bit libraries > # are found in /lib32 and /usr/lib32, /lib64 and /usr/lib64 are symlinks to > # /lib and /usr/lib, while other distributions install libraries into /lib64 > # and /usr/lib64. The LSB does not enforce the use of /lib64 and /usr/lib64, > # it doesn't tell anything about the 32bit libraries on those systems. Set > # MULTILIB_OSDIRNAMES according to what is found on the target. > 9c16 < MULTILIB_OSDIRNAMES = ../lib64 ../lib --- > MULTILIB_OSDIRNAMES = ../lib64 $(if $(wildcard $(shell echo $(SYSTEM_HEADER_DIR))/../../usr/lib32),../lib32,../lib) 15c22,23 < crtbeginT.o crtfastmath.o --- > crtbeginT.o \ > crtfastmath.o 17,21c25,26 < # The pushl in CTOR initialization interferes with frame pointer elimination. < # crtend*.o cannot be compiled without -fno-asynchronous-unwind-tables, < # because then __FRAME_END__ might not be the last thing in .eh_frame < # section. < CRTSTUFF_T_CFLAGS = -fno-omit-frame-pointer -fno-asynchronous-unwind-tables --- > softfp_wrap_start := '\#ifdef __x86_64__' > softfp_wrap_end := '\#endif' tmstaedt@buildlnx2:/localbuild/gcc-4.2.2/gcc/config/i386$ Brian Dessent schrieb: > Tim Prince wrote: > > >> Ubuntu decided to find a 64- vs 32- bit setup incompatible with >> predecessor distros. >> > > Not just Ubuntu, but Debian (and anything based on Debian.) You make it > out to seem like the Debian maintainers did this because they just felt > like being different, but I'm sure they had their own good reasons. > After all, they had to maintain a local patch in their gcc trees to make > it work, so it's not like they didn't also feel the burden of this. If > the distro maintainers thought that the tradeoff of making tens of > thousands of packages easier for their team of maintainers to manage > warrants a two line change in some gcc configury, then that's their > right. > > >> Presumably, there is an ubuntu patch set for this, >> but it's quite inconvenient that they chose to break the scheme chosen >> by their predecessors. The scheme chosen by everyone else is to put the >> 64-bit stuff in /usr/lib64, and the 32-bit stuff in /usr/lib. >> > > The patch to make this alternative layout work has been in mainline gcc > for more than 2 months: > <http://gcc.gnu.org/viewcvs?view=rev&revision=128845> so the issue is > now moot, or at least it will be before too long. > > >> Pretty >> much the kind of mess Bill Gates wanted to see the alternatives get into. >> > > And this is relevant how?!? Yes, it sure does suck that you can't > install gcc in Debian. Oh wait, you can: "apt-get install gcc". > > The fact that Debian maintainers go out of their way to modify and > "Debianize" many software packages sometimes does mean that occasionally > patches are required to get upstream sources to work. This is a feature > not a bug, and it's one of the reasons why I happen to cherish Debian > based systems above all others. If you want something that's just a > bunch of software thrown together without any patches (= without any > cohesion), by all means run far and fast from Debian; it will drive you > crazy. > > Brian > ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Problem building gcc-4.2.2 on 64-bit ubuntu linux 2007-12-20 1:56 ` Tim Prince 2007-12-20 6:17 ` Brian Dessent @ 2007-12-20 7:21 ` Fabian Cenedese 1 sibling, 0 replies; 12+ messages in thread From: Fabian Cenedese @ 2007-12-20 7:21 UTC (permalink / raw) To: gcc-help >Ubuntu decided to find a 64- vs 32- bit setup incompatible with >predecessor distros. Presumably, there is an ubuntu patch set for this, >but it's quite inconvenient that they chose to break the scheme chosen >by their predecessors. The scheme chosen by everyone else is to put the >64-bit stuff in /usr/lib64, and the 32-bit stuff in /usr/lib. Pretty >much the kind of mess Bill Gates wanted to see the alternatives get into. Actually I'd have preferred something similar on Windows than the even messier 64bit stuff in Windows\System32 and the 32bit stuff in Windows\SystemWoW64. Logical, isn't it? Sorry for not contributing something substantial. bye Fabi ^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2007-12-20 13:33 UTC | newest] Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2007-12-19 9:09 Problem building gcc-4.2.2 on 64-bit ubuntu linux 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 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
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).