LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Install VirtualBox on Slackware64 13.37 (multilib) (https://www.linuxquestions.org/questions/slackware-14/install-virtualbox-on-slackware64-13-37-multilib-919307/)

pigkouinos 12-18-2011 05:56 AM

Install VirtualBox on Slackware64 13.37 (multilib)
 
Hi everyone,

I want to install the VirtualBox from slackbuilds.org. I've already setup my multilib system (using Alien Bob's instructions+packages). VirtualBox needs acpica, openjdk, virtualbox-kernel. Should all these these packages (including virtualbox) be built as 32bit? Should I use the compat32 tools? Has anyone done this?

jordanGSU 12-18-2011 10:34 AM

Another option
 
For over a year I've been using the latest binary install for "All Distributions" directly from VirtualBox instead of the SlackBuild version which will most likely be a version or two behind.
https://www.virtualbox.org/wiki/Linux_Downloads

I'm also on multilib now, but I think it was working fine even on the base 64bit Slackware.

markush 12-18-2011 11:00 AM

As far as I know, the slackpackage supports only the 32bit-version of Virtualbox. I'm using the 64bit-installer from this site: https://www.virtualbox.org/wiki/Linux_Downloads

It works very well on my Slackware64-current system. I'm not running multilib.

Markus

pigkouinos 12-18-2011 11:50 AM

Thanks guys, I know the latest binary works just fine. Because I run a recompiled freetype/Qt I wanted to build VirtualBox against my Qt but it's no big deal ;-)

BlackRider 12-18-2011 02:48 PM

Quote:

Has anyone done this?
Yes, I have done it.

It is dead easy. Just install the SlackBuild the same way you would install any other SlackBuild. The only issue is that you might need to recompile the kernel before compiling VirtualBox (VirtualBox' modules need to be compiled with the same version of glibc that was used to compile the kernel, otherwise you risk having defective modules).

I prefer the SlackBuild because of two reasons. The first one is that it allows the package manager to handle the software. The second one is that the VirtualBox version in SlackBuild.org is open-source, while the binary version is not. The latter can be a matter of concern or not, depending on your point of view.


All times are GMT -5. The time now is 04:51 PM.