On 4/2/20 4:22 AM, Stephen Berman via blfs-support wrote:
On the weekend I built LFS SVN-20200319 with jhalfs (it was the first time I tried jhalfs, and it succeeded), and yesterday I wanted to start on BLFS, but when I ran the BLFS/update-lfs.sh script (after fixing a syntax error, which I reported to the blfs-dev list), I saw that LFS had been updated to SVN-20200401, and the following packages have newer versions than the ones I installed: automake, e2fsprogs, elfutils, meson, openssl, perl, xz. So the versions of these packages in /var/lib/jhalfs/BLFS/instpkg.xml conflict with the installed versions. Is it still ok to proceed with the BLFS build? Or should I change the versions of these in instpkg.xml to the installed versions? Or should I update the installed packages, and if so, can I do that without rebuilding any of the other LFS packages?
You can update any of those packages "in place" if desired using the Chapter 6 instructions. You do not have to do that though. However, trying to keep up with the changes in the development version is quite time consuming, especially considering the updates in BLFS. To see how often packages change, just see the change log in each book.
Note that we do not recommend ever trying to change glibc "in place". There is a high probability that the entire system will become unusable when attempting to do that.
-- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
