[SOLVED] Need help compiling VirtualBox for Slackware 14.2 x64

mfoley · 09-02-2016, 09:04 PM

I've just installed a new Slackware x64 14.2 system. Now I am trying to install VirtualBox per instructions and files located at https://slackbuilds.org/repository/1...em/virtualbox/. I've make'd and installed acpica-unix2-20160108 and virtualbox-kernel-5.0.14 per the "This Requires" comment on that link.

When I try to `./configure` in the VirtualBox-5.0.14 directory, I get an error:

Code:

***** Checking 32-bit support *****
compiling the following source file:
#include <stdint.h>
int main(void)
{
  return 0;
}
using the following command line:
gcc -m32 -O -Wall -o /user/util/src/vbox/VirtualBox-5.0.14/.tmp_out /user/util/src/vbox/VirtualBox-5.0.14/.tmp_src.c
In file included from /usr/include/features.h:392:0,
                 from /usr/include/stdint.h:25,
                 from /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/include/stdint.h:9,
                 from /user/util/src/vbox/VirtualBox-5.0.14/.tmp_src.c:1:
/usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory
compilation terminated.

I don't really care about 32 bit support. How can I get past this error?

btw, I do have gnu/stubs-64.h, not gnu/stubs-32.h

speck · 09-02-2016, 09:17 PM

I just download and install the *.run file from the Oracle VirtualBox website, it will work in pure 64 bit Slackware.

guanx · 09-03-2016, 01:46 AM

./configure --disable-vmmraw

kikinovak · 09-03-2016, 07:22 AM

In my package repos, I have VirtualBox for Slackware 14.1 and 14.2. My 64-bit systems are normally "pure", e. g. no 32-bit compatibility layer. The workaround I have found for VirtualBox is to temporarily install 32-bit compatibility packages for gcc and glibc, then build VirtualBox, then go pack to "pure" 64-bit. What sounds like a bit of a hassle is in fact quite simple once you've done it a couple times. Works perfectly.

Cheers,

Niki

mfoley · 09-03-2016, 10:06 AM

Thanks for the responses. I did manage to get past the 32bit failure by installing the 32bit compatability packages from http://alien.slackbook.org/dokuwiki/...kware:multilib. However, my ./configure still fails with:

Code:

Checking for makeself:
  ** makeself (variable makeself) not found!

Any idea what this is about?

I must say, the tarball in the Slackware 14.2 repo for this is certainly a bit lacking. No INSTALL file describing what to do step-wise, no mention of the 32bit issue ...

Next I'll try the *.run from the Oracle site as speck suggested, then kikinovak's suggestion. I'll post back results.

speck: Which oracle site, exactly? I've not found *.run files per se. I've found downloads for various distributions (not Slackware) at https://www.virtualbox.org/wiki/Linux_Downloads.

hitest · 09-03-2016, 10:50 AM

Quote:

Originally Posted by speck

I just download and install the *.run file from the Oracle VirtualBox website, it will work in pure 64 bit Slackware.

Yep. That's what I do.

speck · 09-03-2016, 10:50 AM

Quote:

Originally Posted by mfoley

speck: Which oracle site, exactly? I've not found *.run files per se. I've found downloads for various distributions (not Slackware) at https://www.virtualbox.org/wiki/Linux_Downloads.

Yes, the AMD64 link listed for All distributions (built in EL5...). The Extension Pack is also available on the Oracle website.

mfoley · 09-03-2016, 12:29 PM

Quote:

Originally Posted by speck

Yes, the AMD64 link listed for All distributions (built in EL5...). The Extension Pack is also available on the Oracle website.

The "All distributions" link permitted me to save a file named 'VirtualBox-5.1.4-110228-Linux_amd64.run'. This is apparently a 206,776 line, 83M sh script (?) with blocks and blocks of binary data at the end. Pardon my igorance, but what is this and how do I use it? Do I just execute it?

While I'm asking, should I first uninstall the virtualbox kernel and acpica that I installed previously?

speck · 09-03-2016, 02:33 PM

Yes, you would run/execute it as root just like you would any other script.

Code:

sh ./VirtualBox-5.1.4-110228-Linux_amd64.run

I've never had the SlackBuilds and VirtualBox*.run versions installed at the same time, but just to be safe I would remove any VirtualBox SlackBuilds packages before installing the VirtualBox*.run version. I know that installing via the VirtualBox*.run file will work without needing to install anything from SlackBuilds.

kikinovak · 09-03-2016, 03:10 PM

Quote:

Originally Posted by mfoley

Next I'll try the *.run from the Oracle site as speck suggested, then kikinovak's suggestion. I'll post back results.

Or you can install my VirtualBox packages for Slackware64 14.2 from here:

http://www.microlinux.fr/microlinux/...ackware64/xap/

Make sure acpica is installed. If you don't have it, use this one:

http://www.microlinux.fr/microlinux/...microlinux.txz

Cheers,

Niki

mfoley · 09-04-2016, 09:25 AM

Quote:

Originally Posted by speck

Yes, you would run/execute it as root just like you would any other script.

Code:

sh ./VirtualBox-5.1.4-110228-Linux_amd64.run

I've never had the SlackBuilds and VirtualBox*.run versions installed at the same time, but just to be safe I would remove any VirtualBox SlackBuilds packages before installing the VirtualBox*.run version. I know that installing via the VirtualBox*.run file will work without needing to install anything from SlackBuilds.

I did install that *.run and it worked! However, I did not remove all the other stuff I had previously installed. I do appear to have intermittent problems with the VM hanging up -- unable to click on anything in the VM windows. I'll try reinstalling on a clean machine without the SlackBuild stuff.

kikinovak - I'll try your packages next.

mfoley · 09-04-2016, 12:02 PM

speck: More info: I installed the AMD64.run package on a clean Slackare64 14.2 system. It installed OK, but when I went to create a new Windows 7 VM the only options I have are for 32bit systems. What's up with that? I did not have that problem on the system where I first installed acpica and virtualbox-kernel.

speck · 09-04-2016, 12:33 PM

Quote:

Originally Posted by mfoley

speck: More info: I installed the AMD64.run package on a clean Slackare64 14.2 system. It installed OK, but when I went to create a new Windows 7 VM the only options I have are for 32bit systems. What's up with that? I did not have that problem on the system where I first installed acpica and virtualbox-kernel.

I'm not sure. When I create a new VM the drop down list offers 32bit and 64bit options for Windows. This post might have some useful information.

kikinovak · 09-04-2016, 01:38 PM

FYI, 32-bit compatibility libraries are build dependencies, but not runtime dependencies. Once VirtualBox compiled, you can safely remove them and replace them by "pure" 64-bit gcc and glibc.

commandlinegamer · 09-06-2016, 08:16 AM

Quote:

Originally Posted by mfoley

I've just installed a new Slackware x64 14.2 system. Now I am trying to install VirtualBox per instructions and files located at https://slackbuilds.org/repository/1...em/virtualbox/. I've make'd and installed acpica-unix2-20160108 and virtualbox-kernel-5.0.14 per the "This Requires" comment on that link.

When I try to `./configure` in the VirtualBox-5.0.14 directory, I get an error:

Code:

***** Checking 32-bit support *****
compiling the following source file:
#include <stdint.h>
int main(void)
{
  return 0;
}
using the following command line:
gcc -m32 -O -Wall -o /user/util/src/vbox/VirtualBox-5.0.14/.tmp_out /user/util/src/vbox/VirtualBox-5.0.14/.tmp_src.c
In file included from /usr/include/features.h:392:0,
                 from /usr/include/stdint.h:25,
                 from /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/include/stdint.h:9,
                 from /user/util/src/vbox/VirtualBox-5.0.14/.tmp_src.c:1:
/usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory
compilation terminated.

I don't really care about 32 bit support. How can I get past this error?

btw, I do have gnu/stubs-64.h, not gnu/stubs-32.h

I'm a bit confused. Are you trying to manually do configure, make, make install in the source directory rather than run the SlackBuild script?

FWIW, I downloaded and installed those packages a couple of days ago without issue.