On 2019-02-15 23:55 -0800, Brandon Murry via lfs-dev wrote: > Thanks for everyone's help getting through some of the problems I encountered. > Finally got LFS complete and booted and thought I could share a few things > extra issues I came across using git repositories for GCC and the Linux > kernel. > > Because I'm a weirdo, I want to eventually get my LFS software built directly > from official repositories. For the initial build, I used the provided tar > balls EXCEPT for GCC and Linux. There were a couple of extra issues that > seemed to come from this.
I want to do this automatically to detect any compatibility issues earlier. The problem is we may need something (autoconf, yacc, etc.) in very early stage since many repositories don't supply anything generated (for e.g. configure script). Anyway I'll buy some used server parts to assembly a machine for this. > GCC 9.0.1 (experimental) - I came across an issue after building GCC in > chapter 6 where the linker was still using libraries from the /tools > directory. Not sure what the exact issue here was, but the answer I found > (from a previous version of LFS coincidentally) was to dump the specs file > from GCC and then manually change the linker settings so that the /tools > directory references were replaced with libraries of the final system. This > may be an issue going forward for LFS so I thought I'd share, or maybe I just > did something dumb somewhere else. So our "sed" command editing the specs file is not enough for GCC 9? I don't think so but it may be. > Systemd-240 - There was a Werror build problem with systemd. Warnings > generated from the "Werror=format-overflow=" configuration option halted the > compilation. I can go back and find the offending file if people are > interested. Adding "Wno-error=format-overflow" to the ninja build > configuration options helped systemd to finish compiling with no other errors. > It remains to be seen whatever was causing this warning will wreck the system. > My only idea is that GCC 9.0.1 is being picky in a way that 8.20 is not. This may be a security issue (major systemd bug), some irrevelent warning (minor bug as it breaking the build), or a GCC bug (false warning). Try to investigate a little and make a bug report to upstream. > Linux 5.0.0 - I made a huge mistake in using the git repository to compile the > kernel whereas I used the tarballs to install the Linux headers for 4.20.6. I > decided to just go through with it and see if the system would boot still, and > it appears having a different kernel version from the kernel headers did not > blow everything up. Maybe someone here can let me know how to go back and > reinstall the updated headers without ruining everything or recompiling the > whole system. It's safe. Linus prohibits changes "breaking userspace" unless it have to be done for security reason. You can even upgrade the kernel to any later version. But DO NOT TRY TO UPGRADE KERNEL HEADERS in /usr/include !!! -- Xi Ruoyao <[email protected]> School of Aerospace Science and Technology, Xidian University -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
