[Top][All Lists]

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

Re: -Bstatic and -Bdynamic flags when checking fortran compiler librarie

From: Ralf Wildenhues
Subject: Re: -Bstatic and -Bdynamic flags when checking fortran compiler libraries
Date: Sat, 24 Jan 2009 10:45:47 +0100
User-agent: Mutt/1.5.18 (2008-05-17)

* Christopher Hulbert wrote on Fri, Jan 23, 2009 at 05:26:00PM CET:
> On Fri, Jan 23, 2009 at 1:47 AM, Ralf Wildenhues <address@hidden> wrote:
> >
> > For example, even with this patch, libtool-generated shared libraries
> > will likely not get the right treatment here (whatever that is; it
> > depends upon the libraries we're looking at here).
> That is true that libtool does not handle these flags. I would like to
> patch libtool, but I'm afraid that may be a lot more work and not sure
> I can figure out the "proper" way to do it. It does however work for
> programs that do not use libtool.

OK, but for linking programs, it shouldn't matter all that much whether
some deplib is linked statically or shared, right?

This is not a rhetorical question: it may be disproportionally ugly work
for the user to add the necessary run paths, the compiler support
library in question might be very volatile and as such incompatible
versions might be floating around, so that e.g., adding just one path
to, say, LD_LIBRARY_PATH would not work in a typical setup.

> Being a libtool guru, is such a patch even possible? If so, what's the
> estimate on how much work and how invasive it would be?

I have such a patch.  I could need some support and critical review to
push it:


reply via email to

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