Re: LFS-6.6 test error explanations

2010-03-07 Thread zzflop
On Sun, Mar 07, 2010 at 11:08:54AM -0600, Bruce Dubbs wrote: > zzf...@embarqmail.com wrote: > > > I tried LFS-6.6 using the development jhalfs tool. It built without error. > > Comparing my test log with the above reference, I had the same 8 libmudflap > > failures , but didn't have the other 4. Wh

Re: LFS-6.6 test error explanations

2010-03-07 Thread Bruce Dubbs
zzf...@embarqmail.com wrote: > On Mon, Mar 01, 2010 at 05:36:31PM -0600, Bruce Dubbs wrote: >> I've been analyzing the test errors found when I was building LFS-6.6. >> The logs are at >> >>http://www.linuxfromscratch.org/lfs/build-logs/6.6/ >> > > I tried LFS-6.6 using the development jhalfs

Re: LFS-6.6 test error explanations

2010-03-07 Thread zzflop
On Mon, Mar 01, 2010 at 05:36:31PM -0600, Bruce Dubbs wrote: > I've been analyzing the test errors found when I was building LFS-6.6. > The logs are at > >http://www.linuxfromscratch.org/lfs/build-logs/6.6/ > I tried LFS-6.6 using the development jhalfs tool. It built without error. Compari

Re: LFS-6.6 test error explanations

2010-03-01 Thread Bryan Kadzban
Ken Moffat wrote: > sed-4.2.1 > > 4 failures > FAIL: utf8-1 > FAIL: utf8-2 > FAIL: utf8-3 > FAIL: utf8-4 > > (these are testing case conversion (\u and \U) > for cyrillic I saw this when I had LC_ALL=C on the host. The sed test script only sets individual LC_* variables that it thinks will aff

Re: LFS-6.6 test error explanations

2010-03-01 Thread Ken Moffat
On 1 March 2010 23:36, Bruce Dubbs wrote: > I've been analyzing the test errors found when I was building LFS-6.6. > The logs are at > >   http://www.linuxfromscratch.org/lfs/build-logs/6.6/ > > This is a summary: Thanks for this, it confirms and explains some of what I've found in my own x86_64

LFS-6.6 test error explanations

2010-03-01 Thread Bruce Dubbs
I've been analyzing the test errors found when I was building LFS-6.6. The logs are at http://www.linuxfromscratch.org/lfs/build-logs/6.6/ This is a summary: glibc annexc - long time errors that can be ignored. tst-cpuclock2 - this seems to be triggered by a setting in the kernel fo