Linux: How to statically link against system libs?

Nick Sabalausky a at a.a
Fri Apr 29 22:08:29 PDT 2011


"Alexander" <aldem+dmars at nk7.net> wrote in message 
news:ipfhnu$194o$1 at digitalmars.com...
> On 29.04.2011 22:02, Nick Sabalausky wrote:
>
>> I had been shying away from Alexander's suggestion of uClibc because
>> uClibc's website says it sacrifices speed for size, and because it looks
>> like a royal pain to get set up.
>
>  I am not sure that you would really notice speed difference - but it 
> depends on your application. If you only use it for file/socket I/O, you 
> will hardly notice anything, everything else is in Phobos, thus, 
> independent on libc.
>

Yea, you're probably right.

>  Setting it up, in my experience, is quite easy - but, to be honest, I 
> didn't try it recently, my last experience with uClibc was few years ago. 
> Perhaps, I should try it again...
>

According to the FAQ, they used to support a way that you could use your 
existing GCC toolchain to build uClibc apps, but that turned out to have 
fundamental problems, so now the only way to do it is with a whole separate 
specially-built-for-uClibc version of GCC. And from what I can tell, linux 
(and just "the unix way" in general) doesn't seem to be very good at 
handling multiple forks of the same program installed on the same system 
(unless you use a heretical portable-installation approach like DMD 
thankfully uses).




More information about the Digitalmars-d-learn mailing list