Matthew Burgess wrote:

> So, where now?  In an ideal world (yeah, that's the one where there
> aren't any constraints on time, CPU cycles, etc.!), we would carry out
> ICA tests on the current build order and compare them to the results of
> the same tests run on an alphabetical build.  That way we'd know if
> we've gained anything in terms of reliability/reproducability.

Ken's Farce is probably good enough for our needs. However I did take a
brief look at Greg's scripts and he does a couple of other interesting
things, such as de-compressing all .gz files and un-archiving all .a
files before running the comparison. I didn't get to take an extended
look at it, yet, but I hope to soon. I intend to give my best shot at
running an ICA on the branch. I may look at moving procps up in the
order first, as perl's testsuite needs it.

Also, as I mentioned earlier in this thread, talking with Ryan set me on
a little bit of a purity path. One thing he suggested, however, which
I'm finding hard to put faith in at this point. He mentioned the purity
of the build is shown, in part, by being able to build on old and broken
hosts, ie, RH 6.2. I can see his point, in that it shows we've broken
from that environment and have built ourselves a robust and sane
toolchain. However, current LFS has requirements far above RH 6.2, such
as a host with a 2.6 kernel because of the step up to NPTL.  Also, (at
least with RH 6.0; I don't have 6.2) the version of 'make' is too old to
even parse the 2.6 kernel's make system.  So, to really break free from
such an environment, we'd have to first build a sane set of gnu-tools on
it. Unless I'm missing something, I don't see how showing purity by
building on such old hosts at this time has merit.

Lastly, it's easy to determine a package's binary build-time
dependencies by setting the PATH to be something like '~/bin' and
symlinking binaries into your path as you need them. Run through the
installation of the package and symlink until the errors are gone.
Anyone have a better suggestion and/or one that will help determine
library or run-time dependencies?

--
JH
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to