On 25 Dec 2016, at 19:21, Nikolai Lifanov <lifa...@freebsd.org> wrote: > > I would like to understand why WITH_SHARED_TOOLCHAIN is not the default.
This has been a long standing tradition. Mainly, because you could theoretically rescue yourself out of some bad situations by being able to compile yourself out of it, since statically linked executables won't break if e.g. libc.so or ld-elf.so is screwed up. This is also the reason that /sbin/init and /rescue/rescue are statically linked. Additionally, it could give a minor performance improvement, that is if the slowdown caused by dynamic linking is not offset by reading a larger executable. > My Raspberry Pi 3 is self-hosting with -j4 and doesn't run out of memory > if the toolchain is shared. Is there a downside to this option? I normally always use WITH_SHARED_TOOLCHAIN, and I have yet to encounter any problem with it. -Dimitry
signature.asc
Description: Message signed with OpenPGP using GPGMail
