On Sun, 2014-10-05 at 12:59 +1300, Christopher Gregory wrote: > On Sat, 2014-10-04 at 17:50 +0200, Pierre Labastie wrote: > > Hi, > > > > Guile install the libguile-2.0.so.22.7.2-gdb.scm file into /usr/lib. > > Since it is not an elf library, it gives a warning when running ldconfig. > > Also, I am not sure it may be found by gdb: reading the gdb documentation, I > > would be inclined to move that file to /usr/share/gdb/auto-load. But I see > > that the file libstdc++.so.6.0.20-gdb.py is (manually) moved to > > /usr/share/gdb/auto-load/usr/lib, after building gcc. So I am not sure > > whether > > that should not be the same for libguile-2.0.so.22.7.2-gdb.scm... > > What I am sure about is that files libglib-2.0.so.0.4200.0-gdb.py and > > libgobject-2.0.so.0.4200.0-gdb.py are installed (automatically when the > > respective packages are built) to /usr/share/gdb/auto-load. > > > > Does somebody know more about this? > > > > Pierre > > > > Hello, > > I am glad you brought this up Pierre. > > I hate that non-elf error when running ldconfig. I did do a little > research but all that I managed to find at the time was an answer that > it is not an elf file so the warning is correct and is safe to ignore. > > It just seems that people who answer on a number of mailing lists just > like to post their own thoughts on things without actually answering the > question about how to properly fix it. I guess that those answering > just like to think they are important, rather than shutting up and > letting someone who is actually willing and knows what they are talking > about answer the question. > > I also do not know if having the file in its current location actually > effects the proper update of subsequently installed files. > > I guess that the only way that we may well get a conclusive answer is to > post directly on the main guile developers site and see if we get an > answer. > > Regards, > > Christopher. >
Well I have just done a little more research on this and finally found a sane answer. If I am reading this correctly, we are able to place the offending file anywhere we like so long as we modify gdb's auto-loading-safe-path. More information on this can be found in the following two links: http://sourceware.org/gdb/current/onlinedocs/gdb/Auto_002dloading-safe-path.html#Auto_002dloading-safe-path http://www.gnu.org/software/guile/manual/html_node/GDB-Support.html Regards, Christopher. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
