Failed to compile Virtualbox on Slackware64-current
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Failed to compile Virtualbox on Slackware64-current
Hi,
I'm trying to build Virtualbox on my Slackware64-current machine, but it fails with the following error:
Code:
In file included from /tmp/SBo/VirtualBox-4.2.12/src/libs/xpcom18a4/xpcom/typelib/xpidl/xpidl_idl.c:43:0:
/tmp/SBo/VirtualBox-4.2.12/src/libs/xpcom18a4/xpcom/typelib/xpidl/xpidl.h:49:18: fatal error: glib.h: No such file
or directory
#include <glib.h>
^
You can also install the Oracle standard release which includes support for USB devices and other extended functions. It's not a clean-room OSE, but it does work well for what you need it for if you're willing to fore-go having to have pure open source software on a system.
I agree with @ReaperX7 here. Especially if you are just using the VM to run the evil empire's o/s ! If you want to be purist, then you might as well run Xen or something that's truly 100% open source.
You can also install the Oracle standard release which includes support for USB devices and other extended functions. It's not a clean-room OSE, but it does work well for what you need it for if you're willing to fore-go having to have pure open source software on a system.
Oracle standard release = precompiled OSE. The "extended functions" you are talking about are in the puel-extpack, which is just a set of plugins that works with both. Seriously, if you want a well working vbox get the one from SBo, since Oracle's binary links against libs not available on Slackware (PAM).
I haven't tried building on -current yet so I don't know whether that error is expected or not. Somehow the include path for the glib headers is either missing or the includes are wrong. You can try adding "-I/usr/include/glib-2.0" to CFLAGS and CXXFLAGS as a workaround.
I've always been curious so I tried a build on my slackware64-current with multilib and everything went fine with these patches (but I haven't the possibility to test ATM the resulting packages)
me again.
Based on your suggestions tried to compile again, but still fails with the same error.
Tried to add -I/usr/include/glib-2.0" to CFLAGS and CXXFLAGS and fix to enable compilation with current gcc.
Now the modified virtualbox.SlackBuild contains:
Code:
# Enable GCC 4.8 support
sed -i '417s:7:8:' configure
CFLAGS="$SLKCFLAGS -I/usr/include/glib-2.0"
CXXFLAGS="$SLKCFLAGS -I/usr/include/glib-2.0"
export CFLAGS CXXFLAGS
./configure \
--disable-kmods \
Even then compilation aborts with missing glib.h error, though there is this include file in /usr/include/glib-2.0 path.
I've stored stderr output and it contains following messages at the beginning:
g++ -O -Wall -o /tmp/SBo/VirtualBox-4.2.12/.tmp_out /tmp/SBo/VirtualBox-4.2.12/.tmp_src.cc -I/usr/include/python2.7 /usr/lib/x86_64-linux-gnu/libpython2.7.so
g++: error: /usr/lib/x86_64-linux-gnu/libpython2.7.so: No such file or directory
compiling the following source file: #include <cstdio>
#include <Python.h>
extern "C" int main(void)
I think it's a sane case as later in the log there is another attempt to compile with proper library path /usr/lib64/libpython2.7.so .
have you got a full up-to-date installation of slackware64-current and the latest multilib packages and compat32 ones? I've built the packages on this setup.
I've tried to install suggested x86_64 self-installing package but it requires root privileges and ignores to work under fakeroot as it contains hard-coded paths for logging files etc. I refuse to blindly run anything as root to mess the system so I have to look other way around :-/
have you got a full up-to-date installation of slackware64-current and the latest multilib packages and compat32 ones? I've built the packages on this setup.
I did, all packages updated to current versions, all multilib and compat32 counterparts as well.
I may imagine build requires some undocumented tool as I've no full but menu-driven Slackware install but there is no track about it, no error message making clear what's wrong.
I've tried to install suggested x86_64 self-installing package but it requires root privileges and ignores to work under fakeroot as it contains hard-coded paths for logging files etc. I refuse to blindly run anything as root to mess the system so I have to look other way around :-/
you mean you have run also the slackbuild with fakeroot? that's not supported.
you have to run it in a full-featured root shell, that means logged in as root or becoming root with "su -" (note the "-").
Quote:
Originally Posted by torimus
I've no full but menu-driven Slackware install
if you haven't got a full slackware install (but the KDEI serie) that's not supported either if you want to build anything from SlackBuilds.org.
I've tried to install suggested x86_64 self-installing package but it requires root privileges and ignores to work under fakeroot as it contains hard-coded paths for logging files etc. I refuse to blindly run anything as root to mess the system so I have to look other way around :-/
I always use the installer from Oracle, it works fine and without having to go the multilib path.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Failed to compile Virtualbox on Slackware64-current
