On Wed, Aug 02, 2017 at 06:44:29PM -0500, Bruce Dubbs wrote: > https://sourceware.org/ml/libc-alpha/2017-08/msg00010.html > > One change I see is that the kernel must be 3.2 or later. We will need to > update section 2.2, but I don't think it makes any practical difference. > > GNU Binutils 2.25 or later is now required. This is probably not an issue > for us in Chapter 5 as we build binutils first. We currently require > binutils-2.17. Should we change this? > > gcc-4.9 or later is required. Note that gcc-7.2 is probably going to be > released in the next week or so. > > Please take a look and let us know if you see any other issues we need to > address. > > -- Bruce
These are the sort of things where, if there is a problem, we'll only find out some months after a release when people on very old systems try to build our current release. As with binutils, I would hope we will be using our own gcc from chapter 5 by the time we try to compile glibc. The real problem with updating minimum required versions is finding proof that a version is inadequate. We've been using gcc-4.9 since at least LFS-7.6, and binutils-2.25 since LFS-7.7. I doubt that anyone who wants to build _from_ an older LFS will be using such old systems. I used to try to keep released systems running and patched for known vulnerabilities on at least one machine, but past vulnerabilities in glibc, and my general inability to compile my firefox upgrade stack (including nss, updated cacerts) with gcc versions before gcc-5 (or maybe it was before gcc-6, I forget) caused me to scrap everything older than 7.10. I'm guessing that the best we can do, once gcc-7.2 has been released, is to suck it and see. Or we could just say "Ooh (sucks teeth, shakes head sadly) ... Oh dear. I wouldn't start from *there* if you want to build current LFS." ĸen -- I live in a city. I know sparrows from starlings. After that everything is a duck as far as I'm concerned. -- Monstrous Regiment -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
