Re: linking shared + static system libraries

From: Wieger Wesselink (wieger_at_[hidden])
Date: 2005-07-22 06:52:22

--- In jamboost_at_[hidden], Vladimir Prus <ghost_at_c...> wrote:
> Short answer -- this just won't work.
> 
> Long answer -- with gcc, if you link with a single shared library, 
you link to 
> shared libc. I was told (by binutils maintainer) that it's not 
possible to 
> override this behaviour. Prior versions of Boost.Build tried some 
tricks to 
> force static linking with runtime, and this worked with gcc 2.95, 
but broke 
> with 3.* and at the time I was told it's simply impossible.
> 
> 
> Further, the -static option does not mean "please link to static 
libraries 
> when possible". The linker has an option to *prefer* shared 
libraries to 
> static, and at option to *prevent* linking to shared libraries, but 
no option 
> to *prefer* static libraries. And -static translates in "no shared 
> libraries".
> 
> I don't find this situation satisfactory, say in your case you just 
don't have 
> a static version of a library. However, it's binutils problem. I'd 
be happy 
> to be proved wrong -- do you know a command line that works?

Thanks for the clear explanation. I don't have a solution. In fact, we 
didn't manage to find the proper command line options ourselves, and 
that's why we converted the makefiles to Boost.Build. BTW, this went 
very well, although it was quite a large project.

Regards,

Wieger