/usr/portage/eclass/linux-mod.eclass: line 500: cd: /var/tmp/portage/virtualbox-9999/work/virtualbox-9999/out/linux.x86/release/bin/src: No such file or directory * Preparing vboxdrv module /var/tmp/portage/virtualbox-9999/work/virtualbox-9999/kBuild/gnumake-header.kmk:33: kBuild: Using vanilla GNU make isn't safe for anything but kBuild bootstrapping! Config.kmk:67: *** You must update kBuild!. Stop. !!! ERROR: app-emulation/virtualbox-9999 failed. Call stack: ebuild.sh, line 1546: Called dyn_compile ebuild.sh, line 937: Called src_compile virtualbox-9999.ebuild, line 37: Called linux-mod_src_compile linux-mod.eclass, line 510: Called die !!! Unable to make KERN_DIR=/usr/src/linux all. !!! If you need support, post the topmost build error, and the call stack if relevant. Reproducible: Always
Seems fixed in latest snapshot. Please delete all checkouts of it in your distfiles dir and retry
I still have the problem. During the compilation, the directory /var/tmp/portage/virtualbox-9999/work/virtualbox-9999/out/linux.x86/release/bin/src/ is not created.
Please retry with 1.3.4 which is in tree now
It's the same. Now I know that's the problem isn,t with this application, but I cannot know the right way to install Virtualbox
What I'm getting w/ the 1.3.4 ebuild is the following: -- Source 'env.sh' once before you start to build VBox: source env.sh kmk Enjoy! kmk: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory /usr/portage/eclass/linux-mod.eclass: line 500: cd: /tmp/portage/app-emulation/virtualbox-1.3.4/work/VirtualBox-OSE-1.3.4/out/linux.x86/release/bin/src: No such file or directory * Preparing vboxdrv module /tmp/portage/app-emulation/virtualbox-1.3.4/work/VirtualBox-OSE-1.3.4/kBuild/gnumake-header.kmk:33: kBuild: Using vanilla GNU make isn't safe for anything but kBuild bootstrapping! Config.kmk:67: *** You must update kBuild!. Stop. -- Which is true as I have libstdc++.so.6 (gcc 4.*, glibc 2.5). I'm assuming the package has an executable which is dynamically linked to the older version.
(In reply to comment #5) > What I'm getting w/ the 1.3.4 ebuild is the following: > > [...] > Which is true as I have libstdc++.so.6 (gcc 4.*, glibc 2.5). I'm assuming the > package has an executable which is dynamically linked to the older version. you are right, the kmk binary (part of the kBuild system) is linked to: libstdc++.so.5 so i think sys-libs/libstdc++-v3-3.3.4 will solve the problem
Thank's to all, I fix the problem emerging sys-libs/libstdc++-v3-3.3.4
