Gentoo Forums :: View topic - unable to compile gcc on amd64

unable to compile gcc on amd64

View unanswered posts
View posts from last 24 hours

Gentoo Forums Forum Index

Portage & Programming

View previous topic :: View next topic

Author

Message

Cr0t
l33t
l33t

Joined: 27 Apr 2002
Posts: 944
Location: USA

Posted: Sun Sep 19, 2010 11:16 pm Post subject: unable to compile gcc on amd64

Code:

CFLAGS="-march=core2 -O2 -pipe"
CXXFLAGS="${CFLAGS}"
CHOST="x86_64-pc-linux-gnu"
ACCEPT_KEYWORDS="~amd64"

I am unable to recompile gcc-4.4.4-r2. The problem started out with that sandbox doesn't want to compile and still doesn't compile. Now gcc doesn't recompile, however gcc-4.5.0 recompiles, but a recompilation of either gcc 4.4.4 or sandbox fails. At this point I am trying to roll back to gcc-4.4.4-r2, but the recompilation does not work.

Code:

SYSCALLS.c:1458: warning: conflicting types for built-in function 'vfprintf'
SYSCALLS.c:1464: warning: conflicting types for built-in function 'vprintf'
SYSCALLS.c:1465: warning: conflicting types for built-in function 'vsprintf'
rm -f SYSCALLS.c tmp-SYSCALLS.s
rm gcc.pod
make[3]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build/gcc'
mkdir -p -- x86_64-pc-linux-gnu/libgcc
Checking multilib configuration for libgcc...
Configuring stage 1 in x86_64-pc-linux-gnu/libgcc
configure: creating cache ./config.cache
checking for --enable-version-specific-runtime-libs... no
checking for a BSD-compatible install... /usr/bin/install -c
checking for gawk... gawk
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for x86_64-pc-linux-gnu-ar... /usr/x86_64-pc-linux-gnu/bin/ar
checking for x86_64-pc-linux-gnu-lipo... lipo
checking for x86_64-pc-linux-gnu-nm... /var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build/./gcc/nm
checking for x86_64-pc-linux-gnu-ranlib... /usr/x86_64-pc-linux-gnu/bin/ranlib
checking for x86_64-pc-linux-gnu-strip... /usr/x86_64-pc-linux-gnu/bin/strip
checking whether ln -s works... yes
checking for x86_64-pc-linux-gnu-gcc... /var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether /var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include accepts -g... yes
checking for /var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include option to accept ANSI C... none needed
checking how to run the C preprocessor... /var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include -E
checking whether decimal floating point is supported... yes
checking whether fixed-point is supported... no
checking for __attribute__((visibility("hidden")))... yes
checking whether the target assembler supports thread-local storage... yes
updating cache ./config.cache
configure: creating ./config.status
config.status: creating Makefile
config.status: executing default commands
Adding multilib support to Makefile in /var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/gcc-4.4.4/libgcc
multidirs=32
with_multisubdir=
Running configure in multilib subdirs 32
pwd: /var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build/x86_64-pc-linux-gnu/libgcc
Running configure in multilib subdir 32
pwd: /var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build/x86_64-pc-linux-gnu
mkdir 32
configure: creating cache ./config.cache
checking for --enable-version-specific-runtime-libs... no
checking for a BSD-compatible install... /usr/bin/install -c
checking for gawk... gawk
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for x86_64-pc-linux-gnu-ar... /usr/x86_64-pc-linux-gnu/bin/ar
checking for x86_64-pc-linux-gnu-lipo... lipo
checking for x86_64-pc-linux-gnu-nm... /var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build/./gcc/nm
checking for x86_64-pc-linux-gnu-ranlib... /usr/x86_64-pc-linux-gnu/bin/ranlib
checking for x86_64-pc-linux-gnu-strip... /usr/x86_64-pc-linux-gnu/bin/strip
checking whether ln -s works... yes
checking for x86_64-pc-linux-gnu-gcc... /var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include -m32
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: in `/var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build/x86_64-pc-linux-gnu/32/libgcc':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
make[2]: *** [configure-stage1-target-libgcc] Error 1
make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build'
make[1]: *** [stage1-bubble] Error 2
make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build'
make: *** [bootstrap-lean] Error 2
emake failed
* ERROR: sys-devel/gcc-4.4.4-r2 failed:
* emake failed with bootstrap-lean
*
* Call stack:
* ebuild.sh, line 56: Called src_compile
* environment, line 4947: Called toolchain_src_compile
* environment, line 5542: Called gcc_src_compile
* environment, line 3128: Called gcc_do_make
* environment, line 2915: Called die
* The specific snippet of code:
* emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}" LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} || die "emake failed with ${GCC_MAKE_TARGET}";
*
* If you need support, post the output of 'emerge --info =sys-devel/gcc-4.4.4-r2',
* the complete build log and the output of 'emerge -pqv =sys-devel/gcc-4.4.4-r2'.
* The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.4.4-r2/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.4.4-r2/temp/environment'.
* S: '/var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build'

>>> Failed to emerge sys-devel/gcc-4.4.4-r2, Log file:

>>> '/var/tmp/portage/sys-devel/gcc-4.4.4-r2/temp/build.log'

* Messages for package sys-devel/gcc-4.4.4-r2:

* ERROR: sys-devel/gcc-4.4.4-r2 failed:
* emake failed with bootstrap-lean
*
* Call stack:
* ebuild.sh, line 56: Called src_compile
* environment, line 4947: Called toolchain_src_compile
* environment, line 5542: Called gcc_src_compile
* environment, line 3128: Called gcc_do_make
* environment, line 2915: Called die
* The specific snippet of code:
* emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}" LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} || die "emake failed with ${GCC_MAKE_TARGET}";
*
* If you need support, post the output of 'emerge --info =sys-devel/gcc-4.4.4-r2',
* the complete build log and the output of 'emerge -pqv =sys-devel/gcc-4.4.4-r2'.
* The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.4.4-r2/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.4.4-r2/temp/environment'.
* S: '/var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build'

* IMPORTANT: 4 news items need reading for repository 'gentoo'.
* Use eselect news to read news items.

Code:

checking for __attribute__((visibility("hidden")))... yes
checking whether the target assembler supports thread-local storage... yes
updating cache ./config.cache
configure: creating ./config.status
config.status: creating Makefile
config.status: executing default commands
Adding multilib support to Makefile in /var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/gcc-4.4.4/libgcc
multidirs=32
with_multisubdir=
Running configure in multilib subdirs 32
pwd: /var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build/x86_64-pc-linux-gnu/libgcc
Running configure in multilib subdir 32
pwd: /var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build/x86_64-pc-linux-gnu
mkdir 32
configure: creating cache ./config.cache
checking for --enable-version-specific-runtime-libs... no
checking for a BSD-compatible install... /usr/bin/install -c
checking for gawk... gawk
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for x86_64-pc-linux-gnu-ar... /usr/x86_64-pc-linux-gnu/bin/ar
checking for x86_64-pc-linux-gnu-lipo... lipo
checking for x86_64-pc-linux-gnu-nm... /var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build/./gcc/nm
checking for x86_64-pc-linux-gnu-ranlib... /usr/x86_64-pc-linux-gnu/bin/ranlib
checking for x86_64-pc-linux-gnu-strip... /usr/x86_64-pc-linux-gnu/bin/strip
checking whether ln -s works... yes
checking for x86_64-pc-linux-gnu-gcc... /var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include -m32
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: in `/var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build/x86_64-pc-linux-gnu/32/libgcc':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
make[2]: *** [configure-stage1-target-libgcc] Error 1
make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build'
make[1]: *** [stage1-bubble] Error 2
make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build'
make: *** [bootstrap-lean] Error 2
emake failed
* ERROR: sys-devel/gcc-4.4.4-r2 failed:
* emake failed with bootstrap-lean
*
* Call stack:
* ebuild.sh, line 56: Called src_compile
* environment, line 4947: Called toolchain_src_compile
* environment, line 5542: Called gcc_src_compile
* environment, line 3128: Called gcc_do_make
* environment, line 2915: Called die
* The specific snippet of code:
* emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}" LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} || die "emake failed with ${GCC_MAKE_TARGET}";
*
* If you need support, post the output of 'emerge --info =sys-devel/gcc-4.4.4-r2',
* the complete build log and the output of 'emerge -pqv =sys-devel/gcc-4.4.4-r2'.
* The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.4.4-r2/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.4.4-r2/temp/environment'.
* S: '/var/tmp/portage/sys-devel/gcc-4.4.4-r2/work/build'

I tried "USE="multilib" FEATURES="-sandbox" emerge gcc portage", but it doesn't work.
_________________
cya

©®0t

audiodef
Watchman

Joined: 06 Jul 2005
Posts: 6639
Location: The soundosphere

Posted: Sun Sep 19, 2010 11:19 pm Post subject:

I just had trouble compiling an upgrade for gcc on my server at home. I'll try to remember to see if it's the same version you have trouble with. I just rolled my eyes at it and moved on. On ~arch, someone's always blowing something up and I figured it would fix itself later. Apparently, it does, as you pointed out. _________________ decibel Linux: https://decibellinux.org Github: https://github.com/Gentoo-Music-and-Audio-Technology Facebook: https://www.facebook.com/decibellinux Discord: https://discord.gg/73XV24dNPN

Cr0t
l33t
l33t

Joined: 27 Apr 2002
Posts: 944
Location: USA

Posted: Sun Sep 19, 2010 11:23 pm Post subject:

audiodef wrote:

I just had trouble compiling an upgrade for gcc on my server at home. I'll try to remember to see if it's the same version you have trouble with. I just rolled my eyes at it and moved on. On ~arch, someone's always blowing something up and I figured it would fix itself later. Apparently, it does, as you pointed out.

The problem is even if I got to gcc 4.5.0 sandbox doesn't compile either. Dies with the same issue.

https://forums.gentoo.org/viewtopic-t-844258-highlight-sandbox+cr0t.html
_________________
cya

©®0t

Display posts from previous:

	Gentoo Forums Forum Index Portage & Programming	All times are GMT
Page 1 of 1

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Copyright 2001-2024 Gentoo Foundation, Inc. Designed by Kyle Manna © 2003; Style derived from original subSilver theme. | Hosting by Gossamer Threads Inc. © | Powered by phpBB 2.0.23-gentoo-p11 © 2001, 2002 phpBB Group
Privacy Policy