Basically because of a if [ -d "${LDPATH}" ] statement, it doesn't allow an LDPATH like this: LDPATH="dir1:dir2:dir3" yet, LDPATH parameters in /etc/env.d _do_ allow that. This is a patch to comment out that restriction. This is required for a GCC patch I'm about to submit for multilib support for GCC on amd64
Created attachment 18500 [details, diff] patch to allow multiple paths LDPATH when using gcc-config
gcc-config-1.3.3-r2 has these changes needed for gcc-3.3.1-r5 for amd64
*** Bug 50132 has been marked as a duplicate of this bug. ***
ok, it seems this bug now applies to all archs and not just amd64. since i am on an amd64 box, i never even noticed a problem.. since we seem to already have a fix.
Stupid question - does it have the entries in the correct order in ld.so.conf?
fixed in cvs
martin - from my ld.so.conf: /usr/lib/gcc-lib/x86_64-pc-linux-gnu/3.3.3 /usr/lib/gcc-lib/x86_64-pc-linux-gnu/3.3.3 /usr/lib/gcc-lib/x86_64-pc-linux-gnu/3.4.0 (i have 3.3.3 and 3.4.0 installed at the moment) same order regardless of which compiler is active. yeah... i'd say that's a bug.
Yeah, some nut in portage dev decided that the order in env.d doesn't bother him, and went and sorted it. Might be mistaken though, but I want to remember it did not do it in the past (and why my gcc2/gcc3 installation did the right thing at the time, before I wiped it). Can anybody in portage dev confirm that ld.so.conf entries was not always sorted? This is also sorda a sticky issue with mozilla/firefox/etc.
Oh, and could we add it in the order it appears in /etc/env.d/ ?
Yeah... Looks like the sort has been in since at least October... It's in every version since 2.0.49-r15, at least. It's not present in any portage-2.0.51.
Ok, this should be fine now ...