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 -mike
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Bug-libtool mailing list Bug-libtool@gnu.org http://lists.gnu.org/mailman/listinfo/bug-libtool