Summary: | libtool-1.5.2* fails build-relink test when using LD_LIBRARY_PATH | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Benno Schulenberg <bensberg> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2005.1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
output of demo-make.test
output of demo-inst.test output of build-relink.test |
Description
Benno Schulenberg
2006-01-16 03:24:27 UTC
works fine for me after it fails, go into the builddir and run it by hand, piping the output into a log file: cd /var/tmp/portage/libtool-1.5.22/work/libtool-1.5.22/tests ./build-relink.test >& log Created attachment 77343 [details, diff]
output of demo-make.test
Running ./build-relink.test manually says to first run demo-inst.test, and running that says to first run demo-make.test. So here follow three attachments:
1) demo-make.test.log
2) demo-inst.test.log
3) build-relink.test.log
Created attachment 77344 [details, diff]
output of demo-inst.test
Created attachment 77345 [details]
output of build-relink.test
(Sorry, they were not patches -- force of habit.)
Hmm, when I unset LD_LIBRARY_PATH it works okay -- both manually and emerging. (This variable set in /etc/bash/bashrc for locally-installed drm and GL libs. Had I better set it elsewhere?) using LD_LIBRARY_PATH like that is wrong add a file to your /etc/env.d which declares LDPATH ... running `env-update` will then insert those paths into your ld.so.conf unable to reproduce when using like LD_LIBRARY_PATH ... |