On Sun, Jun 15, 2014 at 11:34:05AM -0400, Baho Utot wrote: > 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. > [ I kept the whole post for context ]
On my builds, the only things in LFS where I specified -j1 were udev variants, and then only because distros seemed to use -j1. For eudev, -jN seems fine (or at least, the reported test failure in 1.6, without any clear indication of what failed, did not appear to be related to a -jN build). In BLFS, I mostly do not run tests. I build the following with -j1 : nss, shared-mime-info, exiv2, ghostscript (my note says it failed to find .libs/libopengpeg which looks like a typo, and I'm not sure if -j1 is still needed with my current options), cdparanoia (I suppose William's comment applies there), json-c, cyrus-sasl, bind. Those last three are not part of my normal builds. ĸen -- Nanny Ogg usually went to bed early. After all, she was an old lady. Sometimes she went to bed as early as 6 a.m. -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
