-----Oorspronkelijk bericht----- Van: arch-dev-public-bounces@archlinux.org [mailto:arch-dev-public- bounces@archlinux.org] Namens Dan McGee Verzonden: woensdag 31 oktober 2007 15:21 Aan: Public mailing list for ArchLinux development Onderwerp: [arch-dev-public] klibc static or shared building
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.
The downside is that your binaries become a lot bigger. You don't want to include a full copy of klibc libraries in each binary in your initcpio image. Then, for the breakage: what could break? The early userspace tools are usually updated at the same time.