[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: link_all_deplibs

From: Christoph Wellner
Subject: Re: link_all_deplibs
Date: Thu, 20 Jan 2005 14:08:28 +0100
User-agent: Opera M2/7.54u1 (Linux, build 892)

On Tue, 18 Jan 2005 18:43:57 +0100, Ralf Wildenhues <address@hidden> wrote:


Also interesting would be:
  objdump -p .libs/lt-clic
  objdump -p /path/to/.libs/

(you can pipe the output through
  egrep 'PATH|NEEDED'
if it's too long for your taste).

The linking-part of the is this (snippet)
        $(top_builddir)/nmm/utils/gdparse/ \
      $(top_builddir)/nmm/base/ \

For both of these, I'd very much like to see what libtool makes out of
these -- post the output of those commands.  To avoid having to ask you
again, please add --debug as first libtool option.  Pack the output
(gzip or preferably bzip2) and attach, like so:
  /bin/sh ../../libtool --debug --mode=link ..... >linklog 2>&1
  bzip2 linklog
  (attach linklog.bz2)

This is now a lot of text (sorry for that) and I hope, the information is
enough. The clic-application also uses functions from libnmmutils.

It's enough to make me suspect a genuine libtool bug, but not enough to
be able to locate or reproduce it.  Actually, I can build most of the
package just fine.

Hi Ralf,

I attached the files you requested.


Using Opera's revolutionary e-mail client:

Attachment: linklog_clic.bz2
Description: application/bzip2

Attachment: linklog_libnmmbase.bz2
Description: application/bzip2

Attachment: objdump_clic
Description: Binary data

Attachment: objdump_libnmmbase
Description: Binary data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]