Emerging Virtualbox 6.1 at the installation stage ends with an error: No such file or directory: 'components'. MAKEOPTS="-j1" Reproducible: Always last 30 lines of the build.log file: kmk_builtin_install --hard-link-files-when-possible -m 0644 -- /var/tmp/portage/app-emulation/virtualbox-6.1.0/work/VirtualBox-6.1.0/src/VBox/Devices/EFI/FirmwareBin/VBoxEFI64.fd /var/tmp/portage/app-emulation/virtualbox-6.1.0/work/VirtualBox-6.1.0/out/linux.x86/release/bin/VBoxEFI64.fd >>> Source compiled. >>> Test phase [not enabled]: app-emulation/virtualbox-6.1.0 >>> Install app-emulation/virtualbox-6.1.0 into /var/tmp/portage/app-emulation/virtualbox-6.1.0/image Traceback (most recent call last): File "/usr/lib/portage/python2.7/doins.py", line 611, in <module> sys.exit(main(sys.argv[1:])) File "/usr/lib/portage/python2.7/doins.py", line 602, in main os.path.dirname(source)): File "/usr/lib/portage/python2.7/doins.py", line 450, in _doins return install_runner.install_file(source, os.path.dirname(dest)) File "/usr/lib/portage/python2.7/doins.py", line 386, in install_file return self._ins_runner.run(source, dest_dir) File "/usr/lib/portage/python2.7/doins.py", line 195, in run sstat = os.stat(source) OSError: [Errno 2] No such file or directory: 'components' * ERROR: app-emulation/virtualbox-6.1.0::gentoo failed (install phase): * doins failed * * If you need support, post the output of `emerge --info '=app-emulation/virtualbox-6.1.0::gentoo'`, * the complete build log and the output of `emerge -pqv '=app-emulation/virtualbox-6.1.0::gentoo'`. * The complete build log is located at '/var/tmp/portage/app-emulation/virtualbox-6.1.0/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-emulation/virtualbox-6.1.0/temp/environment'. * Working directory: '/var/tmp/portage/app-emulation/virtualbox-6.1.0/work/VirtualBox-6.1.0/out/linux.x86/release/bin' * S: '/var/tmp/portage/app-emulation/virtualbox-6.1.0/work/VirtualBox-6.1.0' !!! When you file a bug report, please include the following information: GENTOO_VM= CLASSPATH="" JAVA_HOME="" JAVACFLAGS="" COMPILER="" and of course, the output of emerge --info =virtualbox-6.1.0
Created attachment 599702 [details] build.log
Created attachment 599704 [details] emerge --info
I've just talked to VirtualBox upstream and they told me that beginning with 6.1.0 release there is no longer x86_32 support as host. So all I can (and will) do is to remove x86 keyword from all virtualbox ebuilds that are host related. I'm sorry to tell you this. Upstream said that 6.0.x will keep support for x86_32 until EOL in about six months.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=44b1a5328d2a2e79ddc66c941f7a9fc7632c2994 commit 44b1a5328d2a2e79ddc66c941f7a9fc7632c2994 Author: Lars Wendler <polynomial-c@gentoo.org> AuthorDate: 2019-12-17 11:23:59 +0000 Commit: Lars Wendler <polynomial-c@gentoo.org> CommitDate: 2019-12-17 11:24:22 +0000 virtualbox-6.1 host packages: Farewell x86_32 support Upstream dropped host support for x86_32 systems. Bug: https://bugs.gentoo.org/703068 Package-Manager: Portage-2.3.82, Repoman-2.3.20 Signed-off-by: Lars Wendler <polynomial-c@gentoo.org> app-emulation/virtualbox-additions/virtualbox-additions-6.1.0.ebuild | 2 +- .../virtualbox-extpack-oracle-6.1.0.135406.ebuild | 2 +- app-emulation/virtualbox-modules/virtualbox-modules-6.1.0.ebuild | 2 +- app-emulation/virtualbox/virtualbox-6.1.0.ebuild | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-)
