On Mon, Apr 28, 2014 at 6:21 AM, Miroslav Lachman <000.f...@quip.cz> wrote:
> Kevin Oberman wrote: > >> On Sun, Apr 27, 2014 at 9:28 AM, Jason Selwitz<jselw...@verizon.net> >> wrote: >> > > [...] > > > I don't see an error there. Was this run with MAKE_JOBS_UNSAFE=yes? If >> not, >> the error came from some other job and is in earlier (perhaps much >> earlier) >> output. >> > > Just for the record... > I tried to compile VirtualBox on FreeBSD 10.0 last week. The compilation > always failed until I set DISABLE_MAKE_JOBS=true. Then it went OK. > > I have error messages from compilation: > > First attempt: > > x-4.3.10/src/VBox/Runtime/common/zip/gzipvfs.cpp > kBuild: Compiling RuntimeBldProg - /usr/ports/emulators/ > virtualbox-ose/work/VirtualBox-4.3.10/src/VBox/Runtime/common/zip/zip.cpp > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.10/src/VBox/ > Runtime/common/zip/tarcmd.cpp:165:49: warning: > expression result unused [-Wunused-value] > for (uint32_t iName = 0; papszNames[iName]; iName) > ^~~~~ > kBuild: Compiling RuntimeBldProg - /usr/ports/emulators/ > virtualbox-ose/work/VirtualBox-4.3.10/src/VBox/Runtime/generic/createtemp- > generic.cpp > .. > .. > kBuild: Compiling RuntimeBldProg - /usr/ports/emulators/ > virtualbox-ose/work/VirtualBox-4.3.10/src/VBox/ > Runtime/common/asm/ASMRdMsrEx.asm > kBuild: Compiling RuntimeBldProg - /usr/ports/emulators/ > virtualbox-ose/work/VirtualBox-4.3.10/src/VBox/ > Runtime/common/asm/ASMWrMsrEx.asm > *** Signal 11 > > > Stop. > make[1]: stopped in /usr/ports/emulators/virtualbox-ose > *** Error code 1 > > Stop. > make: stopped in /usr/ports/emulators/virtualbox-ose > > ===>>> make failed for emulators/virtualbox-ose > ===>>> Aborting update > > ===>>> Update for emulators/virtualbox-ose failed > ===>>> Aborting update > > > > Second attempt: > > kBuild: Compiling RuntimeBldProg - /usr/ports/emulators/ > virtualbox-ose/work/VirtualBox-4.3.10/src/VBox/Runtime/generic/ > RTFileQuerySize-generic.cpp > kBuild: Compiling RuntimeBldProg - /usr/ports/emulators/ > virtualbox-ose/work/VirtualBox-4.3.10/src/VBox/ > Runtime/generic/RTFileReadAll-generic.cpp > *** Signal 11 > > > Stop. > make[1]: stopped in /usr/ports/emulators/virtualbox-ose > *** Error code 1 > > Stop. > make: stopped in /usr/ports/emulators/virtualbox-ose > > ===>>> make failed for emulators/virtualbox-ose > ===>>> Aborting update > > ===>>> Update for emulators/virtualbox-ose failed > ===>>> Aborting update > > > On thinrd attempt, I added DISABLE_MAKE_JOBS=true ad compilation was > successful. I don't know why it got Signal 11 before. > > Miroslav Lachman > This indicates that the build, when split into multiple jobs to build faster on mufti-processor systems fails. This is almost always a race condition where the result of one job is needed by another, but has not completed in time. This would explain why everyone does not see this issue. Options can also trigger this. The point of building with DISABLE_MAKE_JOBS=true (or MAKE_JOBS_UNSAFE=yes) is to serialize the build to avoid such cases and toi assure that error messages are all together with the log of the build that generated them. I erred in suggesting MAKE_JOBS_UNSAFE-yes. It is for use in a port's Makefile when it is known to have an issue with multi-job builds. DISABLE_MAKE_JOBS=true is the variable for a user to force serial builds. Sorry for the error! -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com _______________________________________________ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
