Le 30/01/2020 à 17:19, Alan Feuerbacher via blfs-support a écrit : > On 1/29/2020 8:52 PM, Ken Moffat via blfs-support wrote: >> On Wed, Jan 29, 2020 at 07:00:18PM -0700, Alan Feuerbacher via blfs-support >> wrote: >>> I'm building the development version of systemd. >>> >>> After updating various programs listed in the Changelogs for LFS and BLFS, I >>> left linux-5.5 for last. I had upgraded to linux-5.4.13 a few days ago, >>> without trouble. Keeping in mind that glibc-2.30 depends on the linux >>> headers, as stated in the LFS book: > >>> [snip] >>> > [...] Anyway, > here's what the LFS book says in section "6.3.1 Upgrade Issues": > > << If Glibc needs to be upgraded to a newer version, (e.g. from glibc-2.19 to > glibc-2.20), it is safer to rebuild LFS. Though you /may/ be able to rebuild > all the packages in their dependency order, we do not recommend it. >> > > Clear enough, but that says nothing about my problem at hand: what should one > do when the Linux kernel is updated but Glibc remains the same?
I think you have missed this warning on the kernel page: " Warning The headers in the system's include directory (/usr/include) should always be the ones against which Glibc was compiled, that is, the sanitised headers installed in Section 5.6, “Linux-5.4.13 API Headers”. Therefore, they should never be replaced by either the raw kernel headers or any other kernel sanitized headers. " I usually upgrade all the packages on my blfs systems when new versions come along, to test what can go wrong. I've even upgraded sometimes upgraded glibc. But I've never upgraded the kernel headers in /usr/include. That may be needed for a long term system, but since I rebuild everything anyway every 6 months to test the rc's, I've never seen any issue with keeping the initial kernel headers. Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
