[arch-dev-public] klibc static or shared building

[Dan McGee]

On 10/31/07, Thomas Bächler <thomas at archlinux.org> wrote:
> Changes in these versions:
>
> klibc:
> - compile shared binaries by default (somehow this defaults to static in
> klibc 1.5)
> - patch klibc to be able to build klibc-module-init-tools
> - don't build insmod
> - rebuild against 2.6.23 headers
>
> klibc-extras:
> - update to 2.3, removed modprobe
>
> klibc-udev:
> - rebuild for new klibc, enable shared linking again
>
> klibc-module-init-tools:
> - initial commit to the repository (replaces insmod from klibc and
> modprobe from klibc-extras)
>
> mkinitcpio:
> - Fix #8448
> - Change the base hook to work with klibc-m-i-t

Just curious- what is the downside of building statically? It seems
like it could be a plus in some ways, because you eliminate one more
chance of breakage in early userspace. Of course, this also increases
the size of your built binaries and increases the size of your initrd.

-Dan