Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 622444

Summary: =sys-libs/glibc-2.23-r4 - configure: error: LD_LIBRARY_PATH shouldn't contain the current directory when building glibc. Please change the environment variable and run configure again.
Product: Gentoo Linux Reporter: Ladislav Zitka <archenroot>
Component: Current packagesAssignee: Gentoo Toolchain Maintainers <toolchain>
Status: RESOLVED INVALID    
Severity: normal    
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Ladislav Zitka 2017-06-22 08:03:46 UTC
While building glibc I face following error:
=================================================================================
checking for makeinfo... makeinfo
checking version of makeinfo... 6.1, ok
checking for sed... sed
checking version of sed... 4.2.2, ok
checking for gawk... gawk
checking version of gawk... 4.1.3, ok
checking if x86_64-pc-linux-gnu-gcc -m32 -Wl,-O1 -Wl,--as-needed -Wl,--as-needed is sufficient to build libc... yes
checking for i686-pc-linux-gnu-nm... no
checking for nm... nm
checking LD_LIBRARY_PATH variable... contains current directory
configure: error: 
*** LD_LIBRARY_PATH shouldn't contain the current directory when
*** building glibc. Please change the environment variable
*** and run configure again.
 * ERROR: sys-libs/glibc-2.23-r4::gentoo failed (configure phase):
 *   failed to configure glibc

=================================================================================
When I check in the same term session (same env) the actual value it is set to:
ares ~ # echo $LD_LIBRARY_PATH
:/opt/cuda/lib64:/opt/cuda/extras/CUPTI/lib64:/opt/cuda/lib64:/opt/cuda/extras/CUPTI/lib64

I probably do unnecessary following export in /etc/profile:
export LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:/opt/cuda/lib64:/opt/cuda/extras/CUPTI/lib64" 

When I unset the LD_LIBRARY_PATH and try emerge again, the error disappear, but what is the root cause of this?  

===============================================================================
There was another bug reported for older version with similar symptoms:
https://bugs.gentoo.org/show_bug.cgi?id=25045
Comment 1 Jeroen Roovers (RETIRED) gentoo-dev 2017-06-22 10:45:57 UTC
Perhaps you should check your environment for that variable. It certainly isn't a global issue.
Comment 2 Ladislav Zitka 2017-06-22 12:45:36 UTC
I think it is related to:
:/opt/cuda/lib64:/opt/cuda/extras/CUPTI/lib64:/opt/cuda/lib64:/opt/cuda/extras/CUPTI/lib64

the character in the beginning is ":", but it should begin with "/"

I think that could be the issue.
Comment 3 Ladislav Zitka 2017-06-22 12:46:32 UTC
This is related to environment configuration which was not correct in my case.