app-emulation/virtualbox and uic-qt4

[jesterchen]

Hi there,
app-emulation/virtualbox-4.3.10-r2 fails to emerge. The relevant piece of information (as I think) is

[...]
DIR
kmk_builtin_mkdir -p -- /var/tmp/portage/app-emulation/virtualbox-4.3.10-r2/work/VirtualBox-4.3.10/out/linux.amd64/release/obj/VirtualBox/qtuic/
uic VirtualBox - {C}/src/VBox/Frontends/VirtualBox/src/VBoxVMInformationDlg.ui
/usr/bin/uic-qt4 -o /var/tmp/portage/app-emulation/virtualbox-4.3.10-r2/work/VirtualBox-4.3.10/out/linux.amd64/release/obj/VirtualBox/qtuic/VBoxVMInformationDlg.tmp.gen.h /var/tmp/portage/app-emulation/virtualbox-4.3.10-r2/work/VirtualBox-4.3.10/src/VBox/Frontends/VirtualBox/src/VBoxVMInformationDlg.ui
kmk: /usr/bin/uic-qt4: Command not found
kmk: *** [/var/tmp/portage/app-emulation/virtualbox-4.3.10-r2/work/VirtualBox-4.3.10/out/linux.amd64/release/obj/VirtualBox/qtuic/VBoxVMInformationDlg.tmp.gen.h] Error 127
* ERROR: app-emulation/virtualbox-4.3.10-r2::gentoo failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=app-emulation/virtualbox-4.3.10-r2::gentoo'`,
* the complete build log and the output of `emerge -pqv '=app-emulation/virtualbox-4.3.10-r2::gentoo'`.
* The complete build log is located at '/var/tmp/portage/app-emulation/virtualbox-4.3.10-r2/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/app-emulation/virtualbox-4.3.10-r2/temp/environment'.
* Working directory: '/var/tmp/portage/app-emulation/virtualbox-4.3.10-r2/work/VirtualBox-4.3.10'
* S: '/var/tmp/portage/app-emulation/virtualbox-4.3.10-r2/work/VirtualBox-4.3.10'
!!! When you file a bug report, please include the following information:
GENTOO_VM= CLASSPATH="" JAVA_HOME=""
JAVACFLAGS="" COMPILER=""

with

[windex]

First of all, I would like to outline that yes, it is fully possible to run virtualbox in a headless environment. I did this for over a year, for a dev team and certainly had less than 1% downtime, etc., etc.

But you almost certainly aren't trying to do this, this way. What desktop are you using? I'm using LXDE, ergot I have qt4 set in my use flags. I think think vbox uses qt4 for the software gui.

Have you emerged qt4? Have you considered emerging it, and setting in your use flags?

[jesterchen]

I am using fvwm-crystal. I have emerged qt, have qt4 in my useflags (see above).
I have another machine with the same configs, and there I can emerge virtualbox just fine.

I switched to virtualbox-bin on the first machine, so this problem is kind of solved.

Thanks.