From 25231157b9484bfd151181f27f7df87d13209b1a Mon Sep 17 00:00:00 2001 From: Jack Sangdahl Date: Wed, 11 Dec 2024 12:18:26 -0700 Subject: Fix link --- gentoo.html | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) (limited to 'gentoo.html') diff --git a/gentoo.html b/gentoo.html index d170810..7c4c462 100644 --- a/gentoo.html +++ b/gentoo.html @@ -58,7 +58,7 @@ hardware features
kernel
bootloader
- portage
+ system bits
applications
miscellaneous
screenshots @@ -207,18 +207,18 @@ CONFIG_CMDLINE="root=PARTUUID=<uuid> ro" Reboot and the bootable system should be shown in Mac's EFI program. -
+

Other System Bits

C Library

I opted to use musl on this system, over the traditionally used glibc. While there are never-ending debates over which library is better, using musl has some - clear benefits on this machine. Namely, meaning shorter compile times -- - musl compiles in roughly 2 minutes, versus glibc's 2 hours. Omitting glibc - also removes the dependency for GCC, another hefty package. As for the - reduced "compatibility" when using musl, in terms of non-POSIX compliant - code, Flatpak is an adequate solution. I currently use Flatpak packages - for proprietary applications whose binaries are linked against glibc, and + clear benefits on this machine. Namely, shorter compile times -- musl + compiles in roughly 2 minutes, versus glibc's 2 hours. Omitting glibc also + removes the dependency for GCC, another hefty package. As for the reduced + "compatibility" when using musl, in terms of non-POSIX compliant code, + Flatpak is an adequate solution. I currently use Flatpak packages for + proprietary applications whose binaries are linked against glibc, and Firefox, as NodeJS has a strict runtime dependency of GCC.

Compiler

As you may have guessed, this system's default compiler infrastructure is -- cgit v1.2.3