Hi all, i'm just in the process of running thru a modified book including (most of) the version upgrades (linux, e2fsprogs, perl, eudev, bison, openssl) to see what happens using them. I just saw that they has been commited in the minute...
I was to slow in reporting my findings (while compilation and checks are currently still running), but it seems so that the sed in perl regarding the gcc-versions is no longer required. When upgrading LFS packages, i think we should do a quick check on seds or patches created by our own whether they are still required. Thats also true for e2fsprogs-1.45.2 were a fix has been included due to my report of that strange install behavior in case /etc/cron.d does not exist. The option --with-crond-dir=no is no longer required for LFS (while does not harm anyway) as e2fsprogs now does the checking right. I'm also testing the new bc (#4436) which seems to be actively maintained and is now on v2.0.2. Looks like it works well - at least i didn't notice any failures trackable down to bc. Btw, we have statements in gcc echoing a #define STANDARD_STARTFILE_PREFIX_1 etc. to some files. Couldn't that be simplified if we change gcc/gcc.c (the STANDARD_STARTFILE_PREFIXes are defined there)? I'm going to test that when build is finished... -- Thomas -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
