[Top][All Lists]

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

Re: Unwanted shared runtime libraries getting added

From: Ralf Wildenhues
Subject: Re: Unwanted shared runtime libraries getting added
Date: Fri, 8 Oct 2010 19:50:39 +0200
User-agent: Mutt/1.5.20 (2010-08-04)

* Ethan Mallove wrote on Fri, Oct 08, 2010 at 07:26:45PM CEST:
> On Fri, Oct/08/2010 07:14:18PM, Ralf Wildenhues wrote:
> > * Ethan Mallove wrote on Fri, Oct 08, 2010 at 02:42:53PM CEST:
> > > I'm trying to create a library which has no shared library
> > > dependencies using the Intel compilers, but it appears Libtool might
> > > be automatically adding in some -lfoo flags that are forcing the
> > > issue.  How can I tell Libtool to not add the -lfoo flags?
> > 
> > Which libraries are added?  
> libimf and friends.
> >
> > Which of those would you like to avoid?
> If possible, all of the Intel runtime libraries (e.g., libimf,
> libsvml, libintlc).

> > libtool normally adds all direct and indirect library dependencies
> > (the latter only when link_all_deplibs is true, which it currently is
> > everywhere except in the Debian-modified libtool), as well as compiler
> > support libraries.  The indirect deplibs is an obvious issue for at
> > least distributors, the rest is usually the right thing to do.
> > 
> So if I set "link_all_deplibs" to "false", will that turn off the
> "-limf -lsvml ..." we're seeing in the link line?


Does running the link command with --tag=CC "fix" that, i.e., avoid the
libraries for you?

Maybe we should just make postdeps et al overridable with a cache


reply via email to

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