Version checking giving wrong results about mylfs

[krglaws]

On further inspection of your version_check output, it does look like you have acceptable versions, so the code is breaking somewhere... I'll think more about this later

[FinleyVickers]

The version check from the book only prints the current versions of each dependency. It doesn't tell you if they are too out of date. It's up to you to inspect the displayed versions and compare them to the minimums listed in the book.

Since I wanted automate that process, I added the version comparisons so that it will tell you when something is too far behind.

But if you look at the output of the version check you can see that all the dependencies appear to be up to date. It looks like your version checking is not properly checking if it is up to date.

[krglaws]

I moved the dependency check step into an independent part of the build, so now when you run sudo ./build.sh --check it will display the minimum and maximum version limits, and the current versions you have on your system. Unfortunately it will require manually examining the output to confirm that things are all good. Not so bad though. I also added a --verbose option so that it will give a bit more detail (only applies to the download step, but planning on expanding it to the other parts).

I'm glad a few other people have a use for this project. Thanks for your input!

[krglaws]

The version check from the book only prints the current versions of each dependency. It doesn't tell you if they are too out of date. It's up to you to inspect the displayed versions and compare them to the minimums listed in the book.

Since I wanted automate that process, I added the version comparisons so that it will tell you when something is too far behind.

[krglaws]

I'm thinking of just getting rid of this part of the project since it is extremely brittle. Probably replacing it with something like an optional --version-check argument that will only run the script as shown in the book, and not attempt to compare the output with what is on the system. Out of curiosity though, can you paste the output of your gcc --version here?

[FinleyVickers]

I'm thinking of just getting rid of this part of the project since it is extremely brittle. Probably replacing it with something like an optional --version-check argument that will only run the script as shown in the book, and not attempt to compare the output with what is on the system. Out of curiosity though, can you paste the output of your gcc --version here?

Sure!
gcc --version

gcc (GCC) 11.2.0 Copyright (C) 2021 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

BTW the Zlib package is out of date and returns a 404 error, updating the link in the pkgs script to https://zlib.net/zlib-1.2.12.tar.xz will fix it. (Outdated link: https://zlib.net/zlib-1.2.11.tar.xz)

[krglaws]

ok, thanks. I'm working on making the dependency version check more flexible and optional.

And thanks for catching that, I'll fix that as well

[FinleyVickers]

ok, thanks. I'm working on making the dependency version check more flexible and optional.

And thanks for catching that, I'll fix that as well

No problem, thanks! Maybe an option for verbose output as well so it's easier to catch errors? I needed to manually remove the quiet tag from the wget command to find the error due to it just silently exiting the script. Thanks for the script by the way, I've done lfs manually a couple times and have been trying to use ALFS but it only works for v8.0 so this script is really helpful.