how to distribute binary tools
Fri Nov 7 10:06:00 GMT 2008
Well. It's because of libtool and binutil's Makefile. I don't know
which env flag should be overided, but just use
to append the flag '-all-static' after libtool --mode=link command.
I'll try on gcc next.
2008/11/7 Eric Fisher <email@example.com>:
> Configure option '--disable-shared' just disable the share libs to be
> created. But the tools being built is still dynamically linked.
> 2008/11/7 Jason Pernito <firstname.lastname@example.org>:
>> On Fri, Nov 7, 2008 at 4:32 PM, Eric Fisher <email@example.com> wrote:
>>> A silly question. Currently, gcc and binutils are built with shared
>>> libs. I want to know when I try to distribute the tool-chain, do I
>>> need include these .so libraries? If yes, then where should I put them
>> It should be on the same path with where it is now or you can put it
>> somewhere in the other path provided that you create a symlink in the
>> same/exact path of which path they are in when you built them
>>> Anyway, how can I build a fully static tool chain?
>> "Regard your soldiers as your children,
>> and they will follow you into the deepest valleys.
>> Look on them as your beloved sons,
>> and they will stand by you even unto death!"
>> - Sun Tzu, the art of war
More information about the Gcc-help