glibc failing

ca_grover · Posted: Wed Mar 23, 2005 5:59 am Post subject: glibc failing

I'm on a relatively recent install (2 weeks old), and have done an emerge sync, then emerge world to do a quick update of my system. However glibc keeps failing on me and I can't figure out how to fix this. here's the error:

diastelo · Guru Joined: 23 Feb 2004 Posts: 521

I'd look in /etc/ld.so.conf and /etc/ld.so.conf.d, if it exists. Past that, I'd try running ldconfig manually as root.
_________________
"No question is so difficult to answer as that to which the answer is obvious" -- George Bernard Shaw

ca_grover · Posted: Thu Mar 24, 2005 1:13 am Post subject:

Thanks diastelo.

I had no luck looking in /etc/ld.so.conf or trying ldconfig as root. However you pointed me in the right direction. There is a note in the ld.so.conf file to not edit that file directly, but to modify the settings in the files in /etc/env.d. I checked that directory, and found 2 entries for gcc - 05gcc-i686-pc-linux-gnu and 05gcc. Neither of these files had the LD_LIBRARY_PATH variable. Then I remembered that grep is a great tool for finding text in a series of files. So, did

bwallis42 · n00b Joined: 18 Aug 2005 Posts: 1

Thanks! Helped me too.

In my case I found LD_LIBRARY_PATH was being set in /etc/profile.env and /etc/env.d/00basic, in both cases it was being set to /usr/lib which I don't think is necessary. Commented them out and now glibc is building nicely.

I have just been skipping the glibc update for the last few months, never bothered trying to fix it. Now all is good.

nixnut · Posted: Sun Nov 27, 2005 10:18 am Post subject:

Moved from Installing Gentoo to Portage & Programming.
Gentoo is already installed, so not an installing gentoo problem.
_________________
Please add [solved] to the initial post's subject line if you feel your problem is resolved. Help answer the unanswered

talk is cheap. supply exceeds demand

dave_deu · Posted: Sun Apr 30, 2006 7:41 pm Post subject:

I used to have a problem that glibc-2.3.6-r3 would not emerge because "LD_LIBRARY_PATH shouldn't contain the current directory".

I solved this problem after reading your post. The solution was to type as root:

ferreirafm · Posted: Wed Jul 06, 2011 1:35 pm Post subject:

Hi there,
This post seems to be rather old, however, it still useful. The dave_deu way did the trick.
G'Luck,
ferreirafm

step · Apprentice Joined: 16 May 2002 Posts: 198

eruvaer_ohta · n00b Joined: 18 Jul 2007 Posts: 23

I do notice that this thread is ancient, but I can say from experience that googling for glibc emerge failing because of LD_LIBRARY_PATH, it still comes up.
After having used the workaround mentioned by dave_deu several times in the past, I finally decided to try to understand what LD_LIBRARY_PATH does and why glibc complains about it containing the current directory.
As mentioned in https://joshumax.github.io/general/2017/06/08/how-torch-broke-ls.html, a trailing colon in LD_LIBRARY_PATH causes the dynamic linker ld.so to add the current directory. As detailed in the linked article, this can lead to strange bugs and it can actually pose a significant security problem.
Moreover, according to http://xahlee.info/UnixResource_dir/_/ldpath.html and https://www.hpc.dtu.dk/?page_id=1180, it is more generally a very bad idea to set LD_LIBRARY_PATH globally.
In my case, it was set in the root .bashrc from a very old installation of CUDA. So the takeaway for me is to not just unset LD_LIBRARY_PATH for emerging glibc, but to solve the more fundamental problem that this variable is set at all in a global way.