On Nov 1, 2013, at 5:01 AM, Richard wrote:
> I'm struggling to understand why we have differing numbers of tests
> for the same package.
you will se some major differences between clfs and lfs because
graphite tests are ran with our builds.
Sincerely,
William Harrington
--
http://linuxfro
>
> From: William Harrington
>To: Richard ; LFS Support List
>
...
>> # of expected passes92870
>> # of expected failures259
>> # of unsupported tests1096
...
># of expected passes 92152
># of expected failures 263
># of unsupported tests
On Oct 31, 2013, at 8:28 AM, Richard wrote:
> 1. How bad is that error? I have inferred that it is probably
> infrequent - but it does no harm to check...
> (FAIL: g++.dg/asan/asan_test.C -O2 AddressSanitizer_HugeMallocTest
> Ident((char*)malloc(size))[-1] = 0 output pattern test, should ma
On Thu, Oct 31, 2013 at 03:26:35PM +, Richard wrote:
> >
> > From: Ken Moffat
> ...
> >Are you using the 7.4 book or svn ? If you are using gcc-4.8.2
> >then I have no data to offer.
> ...
>
> I am (I hope!) using the plain, normal, generic, unadulterated LFS
>
> From: Ken Moffat
...
>Are you using the 7.4 book or svn ? If you are using gcc-4.8.2
>then I have no data to offer.
...
I am (I hope!) using the plain, normal, generic, unadulterated LFS 7.4 - which
means that I just compiled gcc 4.8.1.
I will proceed under
On Thu, Oct 31, 2013 at 01:28:09PM +, Richard wrote:
> Hello again,
>
> I have finally completed the leviathan task of my first gcc compilation and
> test.
>
> I am encouraged to have only one unexpected failure outside libmudflap.
>
> This leaves me with two questions.
>
> 1. How bad is t
Hello again,
I have finally completed the leviathan task of my first gcc compilation and
test.
I am encouraged to have only one unexpected failure outside libmudflap.
This leaves me with two questions.
1. How bad is that error? I have inferred that it is probably infrequent - but
it does no h
Hi,
I tried to install gcc at the chapter 6. After the command: make -k check, I
got this error:
=== libitm Summary ===
# of expected passes26
# of expected failures3
# of unsupported tests1
make[4]: Leaving directory
`/sources/gcc-build/x86_64-unknown-linux-gnu/libitm/
While running the test suite for GCC in Ch. 6.17 I saw the following:
/sources/gcc-4.7.1/gcc/testsuite/gcc.c-torture/compile/compile.exp ...
WARNING: program timed out.
FAIL: gcc.c-torture/compile/pr37669-2.c -0s (test for erros)
This is running on a Celeron 550MHz with 160MB RAM, so I'm quite
