I've been following the list for about three months now, and during that
time I've built three versions of HLFS: 20060101, 20060108, and
20060220. I've dutifully rebuilt the toolchain for each version (though
not for multiple builds within a version), and it's led me to an
(obvious) realization: I should be able to reuse an "older" toolchain
to build a newer version of the source.
As I read the HLFS book, during Chapter 6 (building the host system),
the path is set to use the tools just built over those in the toolchain
as soon as they are available (the +h). Since almost the first thing we
do in Ch 6 is rebuild glibc and gcc, those should then be used for
building any later code. The only exception is binutils, but since we
don't patch that at all in the toolchain, I gather it should be fine.
So... Is my conclusion that I can reuse an older toolchain (including in
that the binutils-build dir that we need to keep for adjusting the
toolchain later) correct? And if so, how would I know when an older
toolchain is "expired" for a given version of the book?
The only way I can think of to actually test the hypothesis is to build
a system with an older toolchain and the current one, and compare them.
Is there some better way to do this than to recursively test for same
structure and file checksums?
Thanks,
-jps
--
http://linuxfromscratch.org/mailman/listinfo/hlfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
