Re: libtool 1.4 not passing linker directives

[Robert Boehne]

Ian:

Automake uses Libtool to create libraries because it is portable,
it's practially the only thing that is.  One thing you should check,
do you really have to specify what is static?  I belive that under
Linux, the linker will choose shared libs over archives, if that
helps at all.  Perhaps you could train your app to find only
the archive libs at link time rather than add -Wl,Bstatic in
your link line.
Another alternative is to stop using Automake, just use the
Makefile.in that you already generated, and tailor it to
link with exactly the options you're hoping for.
  Did I miss anything?

HTH,

Rob

Ian Peters wrote:
> 
> Well,
> 
> I do realize that it's non-portable, but the number of platforms I'm
> building on is very restricted (the application is only of any real use
> on Linux systems running RPM, dpkg, and a few other special cases).  I'm
> not really intentionally trying to use libtool; I'm just using automake,
> which told me to pass linker directives in the prog_LDADD variable,
> which I did, until it broke, and it seems that libtool 1.4 is what
> changes this behaviour.
> 
> I'm not sure why it's using libtool to link my program -- is this
> necessary, avoidable?
> 
> Ian
> 
> On Sat, 2001-10-06 at 17:15, Peter Eisentraut wrote:
> > Ian Peters writes:
> >
> > > Yes, the end goal is to have all of the libraries between the -Bstatic
> > > and -Bdynamic linked statically, while keeping a dynamic binary against
> > > libc and ld-linux.
> >
> > You do realize that this goal cannot be portably accomplished, so you
> > perhaps shouldn't use libtool?
> >
> > --
> > Peter Eisentraut   address@hidden   http://funkturm.homeip.net/~peter
> >
> 
> _______________________________________________
> Libtool mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/libtool

-- 
Robert Boehne             Software Engineer
Ricardo Software   Chicago Technical Center
TEL: (630)789-0003 x. 238
FAX: (630)789-0127
email:  address@hidden