Summary: | sys-libs/glibc-2.9_p20081201 - /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.1/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lgcc | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Martin Mokrejš <mmokrejs> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | /var/tmp/portage/sys-libs/glibc-2.9_p20081201/temp/build.log |
Description
Martin Mokrejš
2009-01-07 22:58:08 UTC
post the full build log of glibc as an attachment Created attachment 177851 [details]
/var/tmp/portage/sys-libs/glibc-2.9_p20081201/temp/build.log
build.log provided * Building multilib glibc for ABIs: x86 amd64 you cannot mix non-multilib toolchains with and multilib profiles. glibc will build fine as long as your multilib setup is sane (and yes, it builds with or without multilib support). > * Building multilib glibc for ABIs: x86 amd64 > > you cannot mix non-multilib toolchains with and multilib profiles. glibc will > build fine as long as your multilib setup is sane (and yes, it builds with or > without multilib support). But how did I manage that? # grep -v '#' /etc/make.conf CFLAGS="-O2 -pipe -march=nocona" CXXFLAGS="${CFLAGS}" CHOST="x86_64-pc-linux-gnu" USE="-acl amd64 berkdb bzip2 -cli -cracklib crypt -cups -doc dri -fortran gdbm -gnome -gpm hal -iconv -ipv6 -isdnlog java jce -kde -kde2 -kde3 laptop -midi mmx mpich2 -mudflap ncurses -nls nptl nptlonly nsplugin -openmp pam -pcre -perl -pppd python readline -reflection -session -spl sse sse2 ssl syslog tcpd unicode xorg zlib X kerberos" PORTDIR_OVERLAY="/nfslarge/usr/portage" ACCEPT_KEYWORDS="~amd64 amd64" VIDEO_CARDS="vesa nvidia" source /nfslarge/usr/portage/local/layman/make.conf # grep glibc /etc/portage/package.use # you're using a multilib profile. i dont really follow the amd64 guys, so you should ask on the users list or join one of the amd64 channels on irc and ask. (In reply to comment #6) > you're using a multilib profile. i dont really follow the amd64 guys, so you > should ask on the users list or join one of the amd64 channels on irc and ask. > So I managed to convert my nfs server of a cluster of Intel Quad Core x86_64 machines. I selected the multilib profile, same as on my other cluster nodes. I did on one of them: node004# ebuild /nfslarge/usr/portage/sys-libs/glibc/glibc-2.9_p20081201-r1.ebuild compile node004# ebuild /nfslarge/usr/portage/sys-libs/glibc/glibc-2.9_p20081201-r1.ebuild install node004# ebuild /usr/portage/sys-devel/gcc/gcc-4.2.4-r1.ebuild compile node004# ebuild /usr/portage/sys-devel/gcc/gcc-4.2.4-r1.ebuild install Then I moved both /var/tmp/portage/sys-libs/glibc/glibc-2.9_p20081201-r1 and /var/tmp/portage/sys-devel/gcc/gcc-4.2.4-r1 to the nfs server and followed with: nfssrv# ebuild /nfslarge/usr/portage/sys-libs/glibc/glibc-2.9_p20081201-r1.ebuild qmerge nfssrv# ebuild /nfslarge/usr/portage/sys-devel/gcc/gcc-4.2.4-r1.ebuild qmerge I could compile all applications before the fix except sanbox, gcc and glibc. The main reason why then failed was that linker tried to avoid the -lgcc as it seemed to be for a different arch. |