| Summary: | setting LIBPATH in env breaks toolchain.eclass | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Colin Macdonald <cbm> |
| Component: | New packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | 2005.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Colin Macdonald
2005-05-03 23:54:02 UTC
sorry summary had wrong gcc version, should be have -r1: gcc-3.3.5-20050130-r1 that's fine. It complains, but it actually works. It's fixed to not compalin in a newer gcc-config version, so please update your gcc-config. FWIW, anything above my gcc-config version is hardmasked. I will assume then that the gcc-config warning is unrelated to my python linking problem and just rebuild python. Thanks for the quick response! oh sorry, I missed the version number you reported should work with that selected gcc profile... /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5-20050130 should be in your ld search path, so we need to find out why it's not there... can you cat /etc/env.d/05gcc... also, run env-update cat /etc/env.d/05gcc PATH="/usr/i686-pc-linux-gnu/gcc-bin/3.3.5-20050130" ROOTPATH="/usr/i686-pc-linux-gnu/gcc-bin/3.3.5-20050130" MANPATH="/usr/share/gcc-data/i686-pc-linux-gnu/3.3.5-20050130/man" INFOPATH="/usr/share/gcc-data/i686-pc-linux-gnu/3.3.5-20050130/info" LDPATH="/usr/lib/globus-2.4/lib:/usr/lib/gcc-lib/i686-pc-linux-gnu/2.95.3" GCC_SPECS="" don't like the looks of that! it looks like the LDPATH has part of gcc 2.95 cat /etc/env.d/gcc/i686-pc-linux-gnu-3.3.5-20050130 PATH="/usr/i686-pc-linux-gnu/gcc-bin/3.3.5-20050130" ROOTPATH="/usr/i686-pc-linux-gnu/gcc-bin/3.3.5-20050130" LDPATH="/usr/lib/globus-2.4/lib" GCCBITS="32" MANPATH="/usr/share/gcc-data/i686-pc-linux-gnu/3.3.5-20050130/man" INFOPATH="/usr/share/gcc-data/i686-pc-linux-gnu/3.3.5-20050130/info" STDCXX_INCDIR="g++-v3" I tried changing the LDPATH line to: LDPATH="/usr/lib/globus-2.4/lib:/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5-20050130" and then running env-update and relogging in, but gcc-config still reports the errors. for reference: cat /etc/env.d/gcc/i686-pc-linux-gnu-2.95.3 PATH="/usr/i686-pc-linux-gnu/gcc-bin/2.95" ROOTPATH="/usr/i686-pc-linux-gnu/gcc-bin/2.95" LDPATH="/usr/lib/gcc-lib/i686-pc-linux-gnu/2.95.3" MANPATH="/usr/share/gcc-data/i686-pc-linux-gnu/2.95/man" INFOPATH="/usr/share/gcc-data/i686-pc-linux-gnu/2.95/info" STDCXX_INCDIR="g++" CC="gcc" CXX="g++" try re-emerging ~gcc-config-1.3.10 I've done that several times, no effect I can see... I edited /etc/env.d/gcc/i686-pc-linux-gnu-3.3.5-20050130: PATH="/usr/i686-pc-linux-gnu/gcc-bin/3.3.5-20050130" ROOTPATH="/usr/i686-pc-linux-gnu/gcc-bin/3.3.5-20050130" LDPATH="/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5-20050130" GCCBITS="32" MANPATH="/usr/share/gcc-data/i686-pc-linux-gnu/3.3.5-20050130/man" INFOPATH="/usr/share/gcc-data/i686-pc-linux-gnu/3.3.5-20050130/info" STDCXX_INCDIR="g++-v3" (i.e., removed the globus stuff). Now it seems fixed! The globus stuff comes from an overlay for installed accessgrid: http://www-unix.mcs.anl.gov/fl/research/accessgrid/software/releases/current/gentoo.html Does that make this bug invalid since it may involve packages not in the tree? OTOH, the globus stuff still showed up in the /etc/env.d/gcc/ files created by the gcc ebuild... the globus stuff shouldnt have shown up in /etc/env.d/gcc/ files ... the question now is how did it get there I'm at a loss what to check... I've tried re-emerging gcc, with the same results. Any suggestions? Is it worth attaching the globus ebuilds? They look fairly normal to me. well here's a hint from the log file:
* CFLAGS="-march=athlon-xp -O2 -pipe"
* CXXFLAGS="-march=athlon-xp -O2 -pipe"
* Configuring gcc ...
* running gcc-compiler-configure
* configuring for GCC_LANG: c,c++,objc,java,f77
* PREFIX: /usr
* BINPATH: /usr/i686-pc-linux-gnu/gcc-bin/3.3.5-20050130
* LIBPATH: /usr/lib/globus-2.4/lib
* DATAPATH: /usr/share/gcc-data/i686-pc-linux-gnu/3.3.5-20050130
* STDCXX_INCDIR: /usr/lib/globus-2.4/lib/include/g++-v3
* Configuring GCC with:
--enable-version-specific-runtime-libs
--prefix=/usr
--bindir=/usr/i686-pc-linux-gnu/gcc-bin/3.3.5-20050130
--includedir=/usr/lib/globus-2.4/lib/include
--datadir=/usr/share/gcc-data/i686-pc-linux-gnu/3.3.5-20050130
--mandir=/usr/share/gcc-data/i686-pc-linux-gnu/3.3.5-20050130/man
--infodir=/usr/share/gcc-data/i686-pc-linux-gnu/3.3.5-20050130/info
--with-gxx-include-dir=/usr/lib/globus-2.4/lib/include/g++-v3
--host=i686-pc-linux-gnu
--build=i686-pc-linux-gnu
--disable-altivec
--enable-nls
--without-included-gettext
--with-system-zlib
--disable-checking
--disable-werror
--disable-libunwind-exceptions
--disable-multilib
--enable-java-awt=gtk
--enable-languages=c,c++,objc,java,f77
--enable-shared
--enable-threads=posix
--enable-__cxa_atexit
--enable-clocale=gnu
Some of that sure doesn't look healthy! The complete logs are here:
http://www.math.sfu.ca/~cbm/temp/gentoo/
(I didn't attach them because one is 7MiB).
the problem is that globus is exporting 'LIBPATH' into your env which overrides gcc ebuild internal 'LIBPATH' stop exporting that variable :P Ok, for the record, is there anything wrong with other ebuilds setting LIBPATH? In other words, is this an upstream bug or ours? I filed a bug with the AG folk to keep track of this issue: http://bugzilla.mcs.anl.gov/accessgrid/show_bug.cgi?id=1307 this is a portage-gcc specific thing renamed the override variable names to be prefixed with TOOLCHAIN_ |
