On Fri, Nov 16, 2007 at 09:16:11PM +0100, Julio Meca Hansen wrote: > I know that's not absolutely specific to LFS, but more to CLFS (as they > have the updates in their SVN repo), but... > > I don't know if they could be directly applicable but... would they be > useful for the LFS book? I mean... the current toolchain components > (2.18 for binutils, 4.2.2 for gcc and 2.7 for glibc) seems to be like a > good candidate for applying those patches, or do they have to be changed > to use them in a LFS build?
LFS tends not to use unreleased software. There have been *occasional* exceptions made for alpha releases, and of course a lot of patches which fix identified problems. Clfs is a lot more aggressive about using upstream patches which may be only alpha quality. Mostly that works, other times they cause problems (e.g. the glibc update includes one change to powerpc code (the rest is documentation) which seems to break compilation on ppc64). > > Would be interesting to be able to offer users the latest changes to the > toolchain components IMHO > If people want what is in clfs, I'm happy for people to follow it (I edit on both). In fact, getting more testers there would be really useful. For LFS, I haven't seen _any_ obvious benefits from recent toolchain upgrades so I'm more than happy to wait until new versions are formally released. For your own builds, feel free to use all the additional patches you want, but don't forget to mention the variations if you have to ask for help. For the LFS book, patches should usually fix an identifiable bug. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
