Ken Moffat wrote:
On Mon, May 25, 2015 at 04:34:33PM +0100, Ken Moffat wrote:
On Mon, May 25, 2015 at 12:05:52AM -0500, Bruce Dubbs wrote:
Ken Moffat wrote:
Also, the build and tests completed in just over 10 minutes, which
is a lot less than I was expecting (SandyBridge i3, -j4). Colour me
baffled and very much wishing I'd never touched this.
On a jhalfs build, I got:
FAIL: c-c++-common/goacc/acc_on_device-2.c scan-rtl-dump-times expand
"\\(call [^\\n]* acc_on_device" 0
FAIL: c-c++-common/goacc/acc_on_device-2.c scan-rtl-dump-times expand
"\\\\(call [^\\\\n]* acc_on_device" 0
But I only saw one "unexpected failure", but two "unexpected successes".
=== g++ Summary ===
# of expected passes 93236
# of unexpected successes 2
# of expected failures 339
# of unsupported tests 3645
=== gcc Summary ===
# of expected passes 113975
# of unexpected failures 1
# of expected failures 259
# of unsupported tests 1789
[gcc-5.1.0]
Build time is: 51 minutes and 47 seconds at -j4. i7-4700MQ CPU @ 2.40GHz
I don't think you actually got the tests to run. Did you have dejagnu
installed or /tools/bin in your PATH?
-- Bruce
/me looks for a brown paper bag. Thanks for pointing that out.
I've just started building expect...
And 2hr 45min later, my results are not so nice as yours. For gcc I
would start to worry, except that I've seen results at least as bad
when I tried make -j4 check and/or used the wrong ulimit. This is
from Xorg, /tools not available, expect and dejagnu added to /usr,
and this time I took care to ensure that I use 'ulimit -s 32768' and
ran 'make -j1 -k check'.
I'll attach them.
I have run into problems with -j > 1 also.
I think all those pr43051-1.c (etc) tests fail in a full environment, but are
skipped in the LFS Chapter 6 environment. I've seen them in the upstream
results page too. For example:
https://gcc.gnu.org/ml/gcc-testresults/2015-05/msg02857.html
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
