Lessons to be learnt from recent events
herbie at autobotcity.net
Tue Jan 28 19:12:02 PST 2003
> -----Original Message-----
> From: lfs-dev-bounce at linuxfromscratch.org [mailto:lfs-dev-
> bounce at linuxfromscratch.org] On Behalf Of Greg Schafer
> Sent: January 28, 2003 7:03 PM
> To: lfs-dev at linuxfromscratch.org
> Subject: Lessons to be learnt from recent events
> I think it worth mentioning that the recent fsckup with the
> thing could have been picked up much earlier had someone simply ran a
> check" for glibc.
> As someone who has taken pride in trying to improve the core of LFS, I
> guilty that we let this slide for so long and thus caused pain to many
> unsuspecting testers. My excuse is that I've been using the HJ
> that's a different can of worms :) and thus didn't notice the
> It just goes to show how important the toolchain side of things is and
> tightly integrated binutils/gcc/glibc all are. Getting as far as
> quite a big price to pay before realising the system is a bit broken.
> hope AC doesn't hear about this :-)
> On a related note, I'll make mention here that Ryan Oliver and myself
> working on a new initiative to build a pure LFS. You might recall
> post from a few weeks back outlining some new ideas. It is essentially
> angle on the build method focussing on building a correct toolchain.
> initially take the form of a hint. We've been at it for a while now
> hopefully have something concrete in a week or two.
> Unsubscribe: send email to listar at linuxfromscratch.org
> and put 'unsubscribe lfs-dev' in the subject header of the message
While on the subject of "make check", has anyone else noticed that the
perl make check fails I think 3 tests? I haven't bothered to take a look
at exactly what fails (just due to missing packages added later?), but
does anyone have some insight?
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-dev' in the subject header of the message
More information about the lfs-dev