[Top][All Lists]

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

Re: handling of -B with libtool

From: Mike Frysinger
Subject: Re: handling of -B with libtool
Date: Wed, 9 May 2007 11:56:00 -0400
User-agent: KMail/1.9.6

On Wednesday 09 May 2007, Ralf Wildenhues wrote:
> * Mike Frysinger wrote on Tue, May 08, 2007 at 06:34:31PM CEST:
> > -Bstatic would be valid for the compiler driver regardless ... if you had
> > a directory in $PWD named "static" ...
> If you have a directory named static and used that as argument for -B,
> you deserve trouble.  Also, isn't -B to be fed an absolute path?

i'm not saying it's a smart idea, just that it is valid :)

no, i dont believe -B does not require an absolute path ... my limited testing 
shows it doesnt ...

> > unless you mean invoking `ld` directly ?  -B to the compiler driver and
> > -B to the linker have very diff meanings ...
> Sure.  But in general, libtool may invoke either the compiler driver or
> the linker directly.  It doesn't do that for GCC any more, I think, but
> it used to.

so since it's a gcc-only flag, this should be OK i think ...

> > i'm trying to use:
> > LDFLAGS = -B/some/path
> > in the build environment and things break when libtool is involved and it
> > tries to link a shared library because it strips this -B flag ...
> You can work around it using
>   -Wc,-B/some/path
> or
>   -Xcompiler -B/some/path
> for now.

ive moved on to doing it differently in my build system ... i just thought i 
should get this fixed properly in libtool for future versions

thanks for the tips

Attachment: signature.asc
Description: This is a digitally signed message part.

reply via email to

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