[vbox-dev] Problem building 5.0.34 and 5.0.36
Klaus Espenlaub
klaus.espenlaub at oracle.com
Fri Mar 17 10:55:17 UTC 2017
Hi Larry,
On 16.03.2017 20:19, Larry Finger wrote:
> When I try to build RPMs for either 5.0.34 or 5.0.36 on openSUSE 42.1, I
> get the following error:
>
> [ 337s] kmk_builtin_rm -f
> "/home/abuild/rpmbuild/BUILD/VirtualBox-5.0.36/out/linux.amd64/release/obj/manual/en_US/man_VBoxManage-extpack.xml"
>
> [ 337s] , /usr/bin/xsltproc --nonet --xinclude --output
> /home/abuild/rpmbuild/BUILD/VirtualBox-5.0.36/out/linux.amd64/release/obj/manual/en_US/man_VBoxManage-extpack.xml
> /home/abuild/rpmbuild/BUILD/VirtualBox-5.0.36/doc/manual/docbook-refentry-to-manpage-preprocessing.xsl
> /home/abuild/rpmbuild/BUILD/VirtualBox-5.0.36/doc/manual/en_US/man_VBoxManage-extpack.xml
>
> [ 337s] kmk: ,: Command not found
> [ 337s] kmk: ***
> [/home/abuild/rpmbuild/BUILD/VirtualBox-5.0.36/out/linux.amd64/release/obj/manual/en_US/man_VBoxManage-debugvm.xml]
> Error 127
> [ 337s] kmk: *** Waiting for unfinished jobs....
> [ 337s] kmk: ***
> [/home/abuild/rpmbuild/BUILD/VirtualBox-5.0.36/out/linux.amd64/release/obj/manual/en_US/man_VBoxManage-extpack.xml]
> Error 127
> [ 337s] kmk_builtin_append -n
> "/home/abuild/rpmbuild/BUILD/VirtualBox-5.0.36/out/linux.amd64/release/obj/tstDeviceStructSizeRC/tstDeviceStructSizeRC.o.dep"
> ""
> "/home/abuild/rpmbuild/BUILD/VirtualBox-5.0.36/src/VBox/Devices/testcase/tstDeviceStructSizeRC.cpp:"
> ""
> [ 359s] kmk_builtin_append -n
> "/home/abuild/rpmbuild/BUILD/VirtualBox-5.0.36/out/linux.amd64/release/obj/VBoxRemPrimary/target-i386/translate.o.dep"
> ""
> "/home/abuild/rpmbuild/BUILD/VirtualBox-5.0.36/src/recompiler/target-i386/translate.c:"
> ""
>
> Version 5.0.32 builds correctly. I have looked at the differences
> between the two versions, and nothing is obvious. The problem is likely
> due to a difference between some utility in openSUSE 42.1 and the distro
> you use for builds.
No, it isn't distro specific - it's our different build process which
was hiding the typo unfortunately...
In the end it was a forgotten backport to 5.0, fixing a typo (brought to
my attention yesterday by another packager): you need to apply
https://www.virtualbox.org/changeset/63850/vbox
The patch can be retrieved with
https://www.virtualbox.org/changeset/63850/vbox?format=diff
> Any suggestion on where I might look?
Thanks goes to the other packager, he was faster then I with locating
the problem.
Klaus
> Thanks,
> Larry
More information about the vbox-dev
mailing list