On Sunday 25 Sep 2011 16:37:48 Florian Philipp wrote: > Am 25.09.2011 12:53, schrieb Mick: > > I updated gcc and when I ran fix_libtool_files.sh I get this: > > > > # fix_libtool_files.sh i686-pc-linux-gnu-4.4.5 > > > > * Scanning libtool files for hardcoded gcc library paths... > > > > cat: ld.so.conf.d/*.conf: No such file or directory > > > > * [1/5] Scanning /lib ... > > * [2/5] Scanning /usr/lib ... > > * [3/5] Scanning /usr/games/lib ... > > * [4/5] Scanning /usr/i686-pc-linux-gnu/lib ... > > * [5/5] Scanning /usr/local/lib ... > > > > What is this ld.so.conf.d/*.conf which the script cannot find? Should I > > just ignore it? > > You can /probably/ ignore it. I have one file there: > /etc/ld.so.conf.d/05binutils.conf > Content: > /usr/x86_64-pc-linux-gnu/lib > > Hope this helps, > Florian Philipp > > P.S.: That's why it is better to use > `find ld.so.conf.d/ -name '*.conf' | xargs --no-run-if-empty cat` > instead of `cat ld.so.conf.d/*.conf`
Thanks guys, I also have the same file in there, but only on my 64bit box which does _not_ come up with an error: # fix_libtool_files.sh x86_64-pc-linux-gnu-4.4.5 * Scanning libtool files for hardcoded gcc library paths... * [1/11] Scanning /lib ... * [2/11] Scanning /usr/lib ... * [3/11] Scanning /usr/lib64/xulrunner-1.9.2 ... * [4/11] Scanning /lib32 ... * [5/11] Scanning /lib64 ... * [6/11] Scanning /usr/lib32 ... * [7/11] Scanning /usr/lib64 ... * [8/11] Scanning /usr/local/lib ... * [9/11] Scanning /usr/local/lib32 ... * [10/11] Scanning /usr/local/lib64 ... * [11/11] Scanning /usr/x86_64-pc-linux-gnu/lib ... My 32bit boxen which come up with this message have an empty /etc/ld.so.conf.d/ directory. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
