Hi there!
First of all, I am glad to see that a great virtual machine software such as
VirtualBox has been GPL'd!
Anyway, I'm experiencing problems building it. My build system is
VectorLinux 5.8 Standard (Slackware 11 based distro).
I have taken care of all the dependencies, and the configure runs fine using
the following flags and environment variables:
$ LIBRARY_PATH=/usr/X11R6/lib ./configure --with-qt-dir=/usr/lib/qt
I found that other Slackware 11 users had to add the LIBRARY_PATH manually
as well so that the Xcursor headers could be found.
After sourcing the "env.sh" script and running "kmk", the build starts and
goes on for quite a while.
But then it aborts abruptly over undefined references to libiconv_open,
libiconv_close and libiconv:
kmk[3]: Leaving directory /home/easuter/software/src/vbox/src/libs'
kmk[2]: Entering directory /home/easuter/software/src/vbox/src/VBox/Runtime'
kmk[4]: Entering directory libiconv_open'
/home/easuter/software/src/vbox/out/linux.x86/release/bin/VBoxRT.so:
undefined reference to libiconv'
collect2: ld returned 1 exit status
kmk[4]: ***
[/home/easuter/software/src/vbox/out/linux.x86/release/obj/src/VBox/Runtime/testcase/tstCritSect/tstCritSect]
Error 1
The failing command:
@g++ -o
/home/easuter/software/src/vbox/out/linux.x86/release/obj/src/VBox/Runtime/testcase/tstCritSect/tstCritSect
/home/easuter/software/src/vbox/out/linux.x86/release/obj/src/VBox/Runtime/testcase/tstCritSect/tstCritSect.o
/home/easuter/software/src/vbox/out/linux.x86/release/bin/VBoxRT.so
-lpthread -lm -luuid -lrt -ldl
kmk[4]: Leaving directory /home/easuter/software/src/vbox/src/VBox/Runtime'
kmk[2]: *** [pass_binaries_before] Error 2
kmk[2]: Leaving directory /home/easuter/software/src/vbox/src'
kmk: *** [pass_binaries_before] Error 2
In the output I pasted above, you can see the error "undefined reference to
libiconv", unfortunately I wasn't able to copy the other ones referring to
libiconv_open and libiconv_close, but they were there.
I'm at a loss as to what else I can do to fix this issue, since I couldn't
find any other references on the vbox mailing lists to this problem.
I'd really appreciate any help and suggestions that may lead to solving this
inconvenience, it would be a pity to have gotten this far and not be able
to build VirtualBox :(
Cheers,
Eugéne
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
