FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo User

 
 
LinkBack Thread Tools
 
Old 09-25-2011, 10:53 AM
Mick
 
Default ld.so.conf.d/*.conf: No such file or directory

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?
--
Regards,
Mick
 
Old 09-25-2011, 03:37 PM
Florian Philipp
 
Default ld.so.conf.d/*.conf: No such file or directory

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`
 
Old 09-25-2011, 03:55 PM
walt
 
Default ld.so.conf.d/*.conf: No such file or directory

On 09/25/2011 03:53 AM, Mick wrote:
> 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?

I think I have some obsolete files in /etc, which makes this confusing.
#cat /etc/ld.so.conf
# ld.so.conf autogenerated by env-update; make all changes to
# contents of /etc/env.d directory
/usr/local/lib
include ld.so.conf.d/*.conf <======== comes from /etc/env.d/00glibc
/usr/lib/opengl/nvidia/lib
/usr/lib/gcc/i686-pc-linux-gnu/4.5.3
/usr/lib/gcc/i686-pc-linux-gnu/4.5.2
//usr/lib/xulrunner-2.0
/usr/lib/qca2
/usr/lib/qt4
/usr/games/lib

#ls -l /etc/ld.so.conf.d/
-rw-r--r-- 1 root root 27 Mar 24 2011 05binutils.conf

That file seems to be obsolete because both of my current binutils
packages were installed later than March 24.

AFAICT there is nothing on my system that uses /etc/ld.so.conf.d/ at all.
So, I'd say ignore the message.
 
Old 09-25-2011, 05:42 PM
Mick
 
Default ld.so.conf.d/*.conf: No such file or directory

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
 

Thread Tools




All times are GMT. The time now is 07:51 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org