Re: LD_RUN_PATH not adding paths when building with shared libs

In regard to: LD_RUN_PATH not adding paths when building with shared libs,...: >[please cc, as I don't seem to be getting mail from the lists - and my >subscribe confirm messages are not getting to me] > >This is still trying to work out problems on IRIX where a needed library >is not in the defau

Re: Installed vs built library

In regard to: Installed vs built library, Luigi Ballabio said (at 11:23am...: >What am I doing wrong? > >Thanks, > Luigi > >P.S. Almost forgetting: libtool 1.4.3, automake 1.7.6, >autoconf 2.57 The libtool maintainers want to focus their efforts on libtool 1.5, and will likely encourage you

Re: LD_RUN_PATH not adding paths when building with shared libs

Bill Moseley <[EMAIL PROTECTED]> wrote: > So, it seems like the LD_RUN_PATH path is not used when building our > project unless we use --disable-shared: I'm not especially familiar with libtool, but IME, LD_RUN_PATH is ignored if any run-time search directories are given on the command line. So i

LD_RUN_PATH not adding paths when building with shared libs

[please cc, as I don't seem to be getting mail from the lists - and my subscribe confirm messages are not getting to me] This is still trying to work out problems on IRIX where a needed library is not in the default search path (libgcc_s.so.1). Tried using LD_RUN_PATH to point to libgcc but tha

Re: IRIX: Expecting n32 objects

Also sprach [EMAIL PROTECTED]: } I'm not sure if this is an autoconf or libtool question. Sorry for } the dup post to those on both lists. } } I've got someone trying to build on IRIX 6.5 and they get: } [snip] } I'm not clear what o32 and n32 are, but it seems odd that they would not } be mat

Re: running libtool from emacs gud mode

On Wed, 27 Aug 2003, Justin Randall wrote: > > Could libtool handle situations where the frontend is improperly mangled: > libtool > such that it would better handle bad behavior? Libtool is just a shell script. The more complicated it becomes, the slower it will run, and the more hidden bugs i

Installed vs built library

Hi all, it's probably something stupid I'm doing. However, here's the problem. Inside a project I'm building a shared library in a sub-directory and a test-suite executable in another. The related lines of the respective Makefile.am are lib_LTLIBRARIES = libFoo.la and bin_PROGRAMS =

RE: Building .so files only.

Stephen Torri writes: > So by patching my libtool I should be able to put the -shared flag in my > AM_LDFLAGS for the Makefile.am and only get the shared.so file right? Yes, but it makes sense adding it to CFLAGS, too. > ! If the @samp{-static} option is given, then only a @samp{.o} file is > !

IRIX: Expecting n32 objects

I'm not sure if this is an autoconf or libtool question. Sorry for the dup post to those on both lists. I've got someone trying to build on IRIX 6.5 and they get: ./configure --with-zlib=$PUBSROOT/tool/sw/zlib/irix \ --prefix=$PUBSROOT/tools/sw/swish-e/2.4/irix/ \ LDFLAGS=-L$PUBSROOT/tool/sw/zl

Re: Building .so files only.

On Thu, 2003-08-28 at 00:49, Stephen Torri wrote: > On Wed, 2003-08-27 at 01:50, Schleicher Ralph (LLI) wrote: > > > ! If the @samp{-static} option is given, then only a @samp{.o} file is > ! built, even if libtool was configured with @samp{--disable-static}. > > This sounds logically confusing.

Re: running libtool from emacs gud mode

- Original Message - From: "Simon Josefsson" <[EMAIL PROTECTED]> To: "Justin Randall" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, August 26, 2003 7:23 PM Subject: Re: running libtool from emacs gud mode ... > This has been fixed in gud in Emacs HEAD. > > That's excellent

Re: Building .so files only.

On Wed, 2003-08-27 at 01:50, Schleicher Ralph (LLI) wrote: > See , > for more details. So by patching my libtool I should be able to put the -shared flag in my AM_LDFLAGS for the Makefile.am and only get the shared.so file right? I se