Pierre Labastie wrote:
Le 04/10/2014 19:11, Bruce Dubbs a écrit :
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?

I've seen this too.  IIRC think I just deleted it.

Looking at the Makefile.am, they put it in
$(DESTDIR)$(libdir)/$$libname-gdb.scm", but I think that is a mistake.

We could use a sed to change libguile/Makefile.in, but it would be just as
clear to move it explicitly after install.

The point is more "where to put that file" (if we want to use it with gdb),
rather than how to move it. I do not know how to test whether gdb finds it.
I guess I need a test guile program.

Or just delete it. How many of out users are going to try to run gdb for guile? If they do want to do it, they probably know to not delete it and where it goes.

http://www.gnu.org/software/guile/manual/html_node/GDB-Support.html

Seems to be relevant.

I note that on my system I have:

ls /usr/share/gdb/guile -R
/usr/share/gdb/guile:
gdb  gdb.go  gdb.scm

/usr/share/gdb/guile/gdb:
boot.scm experimental.scm iterator.go printing.go support.go types.go experimental.go init.scm iterator.scm printing.scm support.scm types.scm

I would say it goes in /usr/share/gdb/guile/gdb/.

  -- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to