List Info

Thread: Why no "--no-undefined" linker flag?




Why no "--no-undefined" linker flag?
user name
2007-06-10 07:54:38
I'm wondering why the "-Wl,--no-undefined" flag is not set by default so the linker won't allow unresolved symbols from object files when building shared libraries.
Perhaps even "Wl,--no-allow-shlib-undefined" should be used?

I'm just curious why these flags were not used. I think they are quite necessary. Am I missing something?

Re: Why no "--no-undefined" linker flag?
country flaguser name
Russian Federation
2007-06-13 10:05:55
On Sunday 10 June 2007 16:54, eracce wrote:
> I'm wondering why the "-Wl,--no-undefined"
flag is not set by default so the
> linker won't allow unresolved symbols from object files
when building shared
> libraries.
> Perhaps even "Wl,--no-allow-shlib-undefined"
should be used?
> 
> I'm just curious why these flags were not used. I think
they are quite
> necessary. Am I missing something?

If those flags are not default in gcc, why they should be
default in
Boost.Build? 

- Volodya

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )