As an experiment I'm building this on an old dual core Atom processor
with 8 GB RAM.  The GCC tests were very slow (of course) but to my
surprise exited with only the two "unexpected" failures in the
libstdc++ test suite.  However, while the tests were running I noticed
some output to the console of:-

show_signal_message: 6 callbacks suppressed
show_signal_message: 2 callbacks suppressed
show_signal_message: 3 callbacks suppressed
show_signal_message: 3 callbacks suppressed
show_signal_message: 4 callbacks suppressed
show_signal_message: 4 callbacks suppressed
do_trap: 1 callbacks suppressed
show_signal_message: 1 callbacks suppressed
show_signal_message: 1 callbacks suppressed
show_signal_message: 2 callbacks suppressed
show_signal_message: 2 callbacks suppressed
show_signal_message: 1 callbacks suppressed
show_signal_message: 1 callbacks suppressed

Can anybody explain this to me as it's beyond my knowledge, but I'm
assuming that they are kernel messages.  I've tried a web search but I
can't find anything related to it.  The only change I made to the
build was to upgrade the kernel to 4.8.12.

These messages don't appear to have affected the build; everything
seems to be fine, but I would be interested to know what caused them.
I don't remember ever receiving these messages in past builds.

BTW I did remember to set ulimit -s to the required 32768.  Is the x32
increase an arbitrary figure or can it be increased still further?
Does it need to be?

More information that may be useful: the host is running a Btrfs file
system with a two SSD RAID setup.  Despite reading some doubts about
the integrity of Btrfs, I've never experienced any issues with it.

Richard
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Reply via email to