On Sunday, June 15, 2014 03:58:44 PM 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
I have tested -j1 to -j8 baoth on i686 and x_86_64. I ahve a eight core amd with 16GB ram and a very old dual core lapdog with 2 GB ram. Both pass the multi core builds. I have scripted the build with the layout per the bbok and I also have a build that has LFS plus the rpm package manager. Both build system pass multi core builds and are reproducable. The scripts are at: https://github.com/baho-utot/LFS-SCRIPTED https://github.com/baho-utot/LFS-RPM > 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 I can provide log files to show that those packages multi core build as per the book, without error. -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
