On 06/15/2014 08:58 AM, Pierre Labastie wrote:
Le 15/06/2014 14:52, Dan McGhee a écrit :
I know--this is the way LFS is wired--to follow the book precisely. Then all
should be well. If, however, I have a make failure whose cause I can't
determine from the log, how can I recognize it as a failure based on too many
jobs running at the same time? Or, better, failure based on a target
completion before its dependencies are complete.
Try building with "make -j1"... Actually, remove the build directory and
unpack again before that. If the build succeeds with -j1, then it was a
parallel job failure.
According to Baho Utot, all packages in LFS are now "parallel job safe".
Not long ago, I know that dejagnu and man-db were not. With jhalfs automation,
we are conservative, and the list of packages built with -j1 is:
attr autoconf coreutils dejagnu gettext gperf groff man-db vim
However, many of those packages build with -jN. But the tests do not pass.
Pierre
Thank you very much, Pierre. This really helps. Somehow during my
build of {,B}LFS-7.4, -j was set to 8 in MAKEFLAGS. I don't remember
intentionally doing it, and when I discovered the situation I was
surprised. Now I have a solution and something to look at with "hinky"
test failures.
Thanks again.
Dan
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
