It's the only way to be sure.
Compiling is for the weak
>>103252952honestly, its not worth it for regular desktop usage. Its a fun ride though.
>>103252952i recently build the development multilib version (m64, m32, x32) in a VMi saved the scripts i used to build each package, create config files, etc., and repeated the build on a cheap laptop, but at the end i couldn't get the root partition to mountit's a cheap Walmart laptop with one of those 64GB internal SD cards (/dev/mmcblk0) instead of a real SSD, and i thought i built the right drivers in the kernel, but i must have missed something, as i couldn't get the kernel to recognize the block device
What I realized by using Arch for months is how many unnecessary dependencies are installed. Only by carefully controlling compiler flags can you truly debloat your system.Unfortunately, LFS doesn't really help you with this. You're expected to follow the procedures provided
>>103254966>Unfortunately, LFS doesn't really help you with this. You're expected to follow the procedures providedtrue, but i'd point out two thingsone is that if you're not a novice (which you shouldn't be anyway if you're trying LFS) you can try to minimize the base system, with the understanding that it's probably going to require modifying ./configure flags and probably patching certain packagesthe other is that the base LFS system is relatively minimal (compared to even the "server" flavor of mainstream distros), and BLFS divides dependencies into Required, Recommended, and Optional, and you can totally ignore the Optional dependenciesultimately, what constitutes a(n) (un)necessary dependency depends on what you want to do with the system; you can consider GNU coreutils and glibc unnecessary and build a barebones kernel + musl + busybox, but if you want a desktop system or even a webserver with a modern framework, you're gonna have a bad time
