After today update portage I have trouble with compile stabilized glibc 2.9 version. Reproducible: Always Steps to Reproduce: emerge glibc Actual Results: ... checking for makeinfo... makeinfo checking version of makeinfo... 4.13, ok checking for sed... sed checking version of sed... 4.1.5, ok checking for autoconf... autoconf checking whether autoconf works... yes checking whether ranlib is necessary... no 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.9_p20081201-r2 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 3634: Called eblit-run 'src_compile' * environment, line 1234: Called eblit-glibc-src_compile * src_compile.eblit, line 188: Called toolchain-glibc_src_compile * src_compile.eblit, line 121: Called glibc_do_configure 'nptl' * src_compile.eblit, line 98: Called die * The specific snippet of code: * "${S}"/configure ${myconf} || die "failed to configure glibc" * The die message: * failed to configure glibc * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.9_p20081201-r2/temp/build.log'. ... Expected Results: Success compile
Created attachment 195869 [details] build.log
Created attachment 195870 [details] emerge --info
post your `emerge --verbose --info`
Created attachment 196036 [details] emerge --info
reopen
I'm experiencing this as well. My LD_LIBRARY_PATH is '/usr/lib64/mpi/mpi-openmpi/usr/lib64:" If I remove the trailing colon, the emerge succeeds. I don't believe a trailing colon implies searching in the current directory, does it?
(In reply to comment #6) > I'm experiencing this as well. My LD_LIBRARY_PATH is > '/usr/lib64/mpi/mpi-openmpi/usr/lib64:" > If I remove the trailing colon, the emerge succeeds. > I don't believe a trailing colon implies searching in the current directory, > does it? > It used to, but it doesn't for some years now (security risk).
unless i'm missing something, your LD_LIBRARY_PATH is incorrect and you should fix your system. i dont think we want to filter LD_LIBRARY_PATH from glibc as it may be set to something crazy (but correct/usable).
Just an additional note, this still occurs if you have the colon at the start of the LD_LIBRARY_PATH. So a naive person like me might write in their .bashrc export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/opt/ati-stream-sdk/include/ And if LD_LIBRARY_PATH is unset glibc fails to compile.
unless ati installs libraries into a dir named "include", that looks like a bogus path to add in the first place ... export LD_LIBRARY_PATH=${LD_LIBRARY_PATH:+${LD_LIBRARY_PATH}:}:/some/path
