Hi,
in our project, we mainly use C++-Code. But for speeding-up things,
sometimes we need to compile assembler-code too. In the past, we used
libtool 1.4.2a on debian woody. We had no problems. But with the new
debian sarge, with libtool 1.5.6, we can't compile our software anymore.
When I
Hi,
I have a problem with libtool-1.5.6, when I want to start my compiled app,
I get an error-message, that some libraries are not found:
/home/chwellner/nmm2_sarge/apps/clic/.libs/lt-clic: error while loading
shared libraries: libnmmutils.so.0: cannot open shared object file: No
such file o
2004-11-03 at 15:08 +0100, Christoph Wellner wrote:
I have a problem with libtool-1.5.6, when I want to start my compiled
app,
I get an error-message, that some libraries are not found:
/home/chwellner/nmm2_sarge/apps/clic/.libs/lt-clic: error while loading
shared libraries: libnmmutils.so.0:
em. I'm using debian sarge.
Perhaps does someone know, how to set the variable 'link_all_deplibs' from
commandline. Perhaps with a spacial tag?
Christoph
On Thu, 4 Nov 2004 09:31:38 +0100, Ralf Wildenhues
<[EMAIL PROTECTED]> wrote:
* Christoph Wellner wrote on Wed, Nov 03,
Hi,
i have trouble starting my application since I get undefined references.
As source I determined the variable "link_all_deplibs_CXX" wich is
explicitly set to 'no' in libtool.m4.
I'm running libtool-1.5.6 under debian Sarge and the problem is, that the
libtool.m4-file is different from the
On Fri, 14 Jan 2005 16:26:22 +0100, Ralf Wildenhues
<[EMAIL PROTECTED]> wrote:
Hi Christoph,
* Christoph Wellner wrote on Fri, Jan 14, 2005 at 04:07:21PM CET:
i have trouble starting my application since I get undefined references.
As source I determined the variable "link_all_deplib
On Fri, 14 Jan 2005 16:26:22 +0100, Ralf Wildenhues
<[EMAIL PROTECTED]> wrote:
[...]
You can either change `libtool.m4' and/or whereever the package you are
talking about stores its m4 macros then rebuild the package or you can
change generated `libtool' -- look for all instances of
link_all_dep
[...]
If you install libA as libtool library (i.e., libA.la is installed as
well), then this should work. libA.la should contain the information
that it depends on libB, that is, if you supplied that at the time of
creating libA.la.
Even if libtool does not state it in its documentation as of now:
On Mon, 17 Jan 2005 16:03:46 +0100, Ralf Wildenhues
<[EMAIL PROTECTED]> wrote:
...
This is all not helpful. Please read[1].
Please provide a small recipe how we can reproduce what you are doing,
or at least post the rules you use to create your libraries and
programs, i.e., Makefile or Makefile
On Tue, 18 Jan 2005 18:43:57 +0100, Ralf Wildenhues
<[EMAIL PROTECTED]> wrote:
Hi Ralf
[...]
The linking-part of the Makefile.am is this (snippet)
$(top_builddir)/nmm/utils/gdparse/libnmmgdparse.la \
$(top_builddir)/nmm/base/libnmmbase.la \
$(top_builddir)/nmm/base/graph/lib
On Tue, 18 Jan 2005 18:43:57 +0100, Ralf Wildenhues
<[EMAIL PROTECTED]> wrote:
[...]
Also interesting would be:
objdump -p .libs/lt-clic
and
objdump -p /path/to/.libs/libmnnbase.so
(you can pipe the output through
egrep 'PATH|NEEDED'
if it's too long for your taste).
The linking-part of th
11 matches
Mail list logo
