>>> Source prepared. >>> Configuring source in /var/tmp/portage/app-emulation/virtualbox-4.3.28/work/VirtualBox-4.3.28 ... Checking for environment: Determined build machine: linux.amd64, target machine: linux.amd64, OK. Checking for kBuild: found, OK. Checking for gcc: ** gcc version 5.1.0 found, expected gcc 3.x with x>1 or gcc 4.x with 0<x<10! Check /var/tmp/portage/app-emulation/virtualbox-4.3.28/work/VirtualBox-4.3.28/configure.log for details * ERROR: app-emulation/virtualbox-4.3.28::gentoo failed (configure phase): * configure failed * * Call stack: * ebuild.sh, line 93: Called src_configure * environment, line 5943: Called die * The specific snippet of code: * ./configure --with-gcc="$(tc-getCC)" --with-g++="$(tc-getCXX)" --disable-kmods --disable-dbus --disable-devmapper ${myconf} || die "configure failed" *
after removing the gcc check in configure I was able to let it compile a lot. Until this error: pdflatex: not found pdflatex: not found pdflatex: not found pdflatex: not found pdflatex {T}/manual/en_US/UserManual.tex (four passes) -> {T}/manual/en_US/UserManual.pdf /usr/bin/kmk_redirect -w+ti /dev/null -C /var/tmp/portage/app-emulation/virtualbox-4.3.28/work/VirtualBox-4.3.28/out/linux.amd64/release/obj/manual/en_US -- pdflatex -interaction batchmode UserManual.tex kmk_redirect: error: _execvp(_P_WAIT, "pdflatex", ...) failed: No such file or directory kmk: *** [/var/tmp/portage/app-emulation/virtualbox-4.3.28/work/VirtualBox-4.3.28/out/linux.amd64/release/obj/manual/en_US/UserManual.pdf] Error 1
and why does it something with "UserManual" when USE="-doc" ? do we need -handbook or something? [ebuild U ] app-emulation/virtualbox-4.3.28::gentoo [4.3.26::gentoo] USE="additions alsa extensions java opengl pam pulseaudio python qt4 sdk udev vnc -doc -headless -vboxwebsrv" PYTHON_TARGETS="python2_7" 0 KiB
pdflatex is part of dev-texlive/texlive-latex-2014. After installing that the error changes: INST generate_service_file => {C}/out/linux.amd64/release/bin/helpers/generate_service_file kmk_builtin_install --hard-link-files-when-possible -- /var/tmp/portage/app-emulation/virtualbox-4.3.28/work/VirtualBox-4.3.28/out/linux.amd64/release/obj/generate_service_file/generate_service_file /var/tmp/portage/app-emulation/virtualbox-4.3.28/work/VirtualBox-4.3.28/out/linux.amd64/release/bin/helpers/generate_service_file pdflatex {T}/manual/en_US/UserManual.tex (four passes) -> {T}/manual/en_US/UserManual.pdf /usr/bin/kmk_redirect -w+ti /dev/null -C /var/tmp/portage/app-emulation/virtualbox-4.3.28/work/VirtualBox-4.3.28/out/linux.amd64/release/obj/manual/en_US -- pdflatex -halt-on-error -interaction batchmode UserManual.tex This is pdfTeX, Version 3.14159265-2.6-1.40.15 (TeX Live 2014) (preloaded format=pdflatex) restricted \write18 enabled. entering extended mode kmk: *** [/var/tmp/portage/app-emulation/virtualbox-4.3.28/work/VirtualBox-4.3.28/out/linux.amd64/release/obj/manual/en_US/UserManual.pdf] Error 1
How I got the package merged: emerge with USE="doc" (fails at virtualbox because of gcc check) Now we have a ton of depending latex stuff installed. clear portage temp dir ebuild unpack modify Configure to give always success on gcc version. ebuild merge The pdflatex bugs only exist if some latex packages are missing. Is "-doc" broken? app-emulation/virtualbox-4.3.28::gentoo was built with the following: USE="additions alsa extensions java opengl pam pulseaudio python qt4 sdk udev vnc -doc -headless -vboxwebsrv" ABI_X86="64" PYTHON_TARGETS="python2_7"
I can confirm the issue and disabling the gcc check helps.
Created attachment 404276 [details, diff] disable gcc check
*** This bug has been marked as a duplicate of bug 555052 ***
*** Bug 556140 has been marked as a duplicate of this bug. ***
Not fixed in virtualbox-5.0.2 .
Created attachment 409242 [details, diff] disable gcc check virtualbox-5.0.2 does the same as the other patch applies to virtualbox-5.0.2
(In reply to jospezial from comment #10) > Created attachment 409242 [details, diff] [details, diff] > disable gcc check virtualbox-5.0.2 > > does the same as the other patch > > applies to virtualbox-5.0.2 And still needed for app-emulation/virtualbox-5.0.4
fixed in virtualbox-5.0.6
Bug is back again with gcc-5.3 When will they ever disable that version check?
I confirm too that VirtualBox emerge break at gcc check with gcc 5.3: >>> Emerging (1 of 1) app-emulation/virtualbox-5.0.10::gentoo * VirtualBox-5.0.10.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) [ ok ] * virtualbox-5.0.2-patches-01.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) [ ok ] * You have disabled the "python" USE flag. This will only * disable the python bindings being installed. >>> Unpacking source... >>> Unpacking VirtualBox-5.0.10.tar.bz2 to /gentoo/tmp/portage/app-emulation/virtualbox-5.0.10/work >>> Unpacking virtualbox-5.0.2-patches-01.tar.xz to /gentoo/tmp/portage/app-emulation/virtualbox-5.0.10/work >>> Source unpacked in /gentoo/tmp/portage/app-emulation/virtualbox-5.0.10/work >>> Preparing source in /gentoo/tmp/portage/app-emulation/virtualbox-5.0.10/work/VirtualBox-5.0.10 ... * Applying various patches (bugfixes/updates) ... * 001_virtualbox-ose-3.2.8-mesa-check.patch [ ok ] * 002_virtualbox-5.0.0_beta3-remove-configure-checks.patch [ ok ] * 003_virtualbox-4.0.2-restore_old_machines_dir.patch [ ok ] * 004_virtualbox-4.1.2-vboxpci-build.patch [ ok ] * 005_virtualbox-4.2.26-asneeded.patch [ ok ] * 006_virtualbox-4.2.18-vboxwebsrv_fix.patch [ ok ] * Skipping 007_virtualbox-4.3.16-gsoap2813.patch due to EPATCH_EXCLUDE ... * 008_virtualbox-4.3.14-missing_define.patch [ ok ] * 050_virtualbox-5.0.2-nopie.patch [ ok ] * Done with patching >>> Source prepared. >>> Configuring source in /gentoo/tmp/portage/app-emulation/virtualbox-5.0.10/work/VirtualBox-5.0.10 ... Checking for environment: Determined build machine: linux.amd64, target machine: linux.amd64, OK. Checking for kBuild: found, OK. Checking for gcc: ** gcc version 5.3 found, expected gcc 3.x with x>1 or gcc 4.x with 0<x<10 or gcc 5.2!
*** Bug 568492 has been marked as a duplicate of this bug. ***
The problem is still there in app-emulation/virtualbox-5.0.10 on ~amd Checking for gcc: ** gcc version 5.3 found, expected gcc 3.x with x>1 or gcc 4.x with 0<x<10 or gcc 5.2! Check /var/tmp/portage/app-emulation/virtualbox-5.0.10/work/VirtualBox-5.0.10/configure.log for details * ERROR: app-emulation/virtualbox-5.0.10::gentoo failed (configure phase):
> The problem is still there in app-emulation/virtualbox-5.0.10 on ~amd Can confirm, with gcc 5.3.0.
*** Bug 568574 has been marked as a duplicate of this bug. ***
Same here, gcc 5.3.0
5.3 compatibility is fixed in 5.0.12
Switching to Gcc 4.x will not fix this since 5.x and 4.x C++ ABI is incompatible.
This should be fixed in >=5.0.16-r1 since: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f83513963afe06880885c2def91b267ccb6bc4e7 app-emulation/virtualbox: Remove pointless GCC limitations
