FreeBSD Port: emulators/virtualbox-ose

[Jason Selwitz]

On 04/28/2014 13:56, Kevin Oberman wrote:
> On Mon, Apr 28, 2014 at 6:21 AM, Miroslav Lachman <000.fbsd at quip.cz
> <mailto:000.fbsd at quip.cz>> wrote:
> 
>     Kevin Oberman wrote:
> 
>         On Sun, Apr 27, 2014 at 9:28 AM, Jason
>         Selwitz<jselwitz at verizon.net <mailto:jselwitz at 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: rkoberman at gmail.com <mailto:rkoberman at gmail.com>


Hello again Everyone, so after trying these suggestions seems like I'm
still unable to upgrade Virtualbox, I would be happy to supply
additional output, I appreciate any suggestions you can provide. thanks
again!

Jason