Expat Tarball Not Recognized | A REALLY Simple How To Fix
If you're reading this you probably have issues with Expat when reaching stage 4 of the building process.
Fixing it is as easy as editing 1 file, that of course if you don't mind doing some bit of nano.
edit file packages.sh in line:17:export PKG_EXPAT=
normally it would have the link for version "2.5.0"
that version is slightly old by now, so i would recommend changing the link to something like 2.6.2 or newer if given the case.
other possible fix is to go to the LFS' Sources directory(./mnt/lfs/sources) and using sudo wget [LINK_TO_NEW_EXPAT_VERSION] then remove the old version and use mv to rename it to 2.5.0, this way it will untar the new version as the old one, and build it as normal.
(NOTE: this last one worked for me more out of the box, as well it was the most simple of these, if we don't count that editing one file is fairly simple already)
Hope someone out there finds this small note useful!.
OS Tested on: Debian GNU/Linux 12 x86_64 (Minimal Installation | NO-GUI.)
Hey thanks for pointing that out. This script is a bit out dated, so its no surprise that some packages need to have their versions updated. I'm hoping to update this whole thing to LFS v 12 at some point in the coming months.
As a note for myself, I might consider adding a --multilib build, so that it can support progressing into GLFS
Hey thanks for pointing that out. This script is a bit out dated, so its no surprise that some packages need to have their versions updated. I'm hoping to update this whole thing to LFS v 12 at some point in the coming months.
Sorry for intruding in 10(almost 11) months later. If you plan to do so, please also leave a guide on manual script upgrading, or a script so the scripts will get upgraded by themselves as LFS updates more.
Also, one more question, there's a templates folder. Can we change it's insides?
Best wishes, Onyx Adrienne Blackhawk Here's to the future of myLFS!