VirtualBox on Slackware: How?

pannet1 · 02-22-2008, 01:45 AM

Hi,

I choose the difficult part of compiling my own Virtual Box. I am able to follow the procedures given in the beginning of the thread. However, I compiled stalled due to the IASL (Intel ACPI compiler).

It does not have a make install and hence I do not know how to tell the Virutualbox ./configure how to find the IASAL. Can anyone let me know how you do it ?

Thanks.

distrubtion: migrated from fedora to slackware

ppr:kut · 02-22-2008, 02:35 AM

You can use my SlackBuild from SlackBuilds.org.

http://slackbuilds.org/repository/12...opment/acpica/

Most of the other deps are there as well, only one missing for the most recent version is pulseaudio and its dependencies.
I have a made a SlackBuild for those too, but don't consider them stable yet. A build script for VirtualBox is also in the works

.

Good Luck!

pannet1 · 02-22-2008, 07:23 AM

wow, great work. i guess one day this will became the repository for slackware. one suggestion you could provide compressed packgage for slax as well.

another thing i noticed is ..
if i change the url http://slackbuilds.org/repository/12...opment/acpica/
to http://slackbuilds.org/repository/11...opment/acpica/

the page has empty values for
Approved by:

may be the webmaster can remove it dynamically.

i have another doubt. what is a slacbuild ? please let me know if you have time.

best regards

ppr:kut · 02-22-2008, 11:44 AM

Quote:

Originally Posted by pannet1

another thing i noticed is ..
if i change the url http://slackbuilds.org/repository/12...opment/acpica/
to http://slackbuilds.org/repository/11...opment/acpica/

the page has empty values for
Approved by:

may be the webmaster can remove it dynamically.

That's because there is no version for Slackware 11. But you're right. Some indication for that might be good.

Quote:

Originally Posted by pannet1

i have another doubt. what is a slacbuild ? please let me know if you have time.

No problem, but I'm really bad in describing such things. Take a look at http://slackwiki.org/SlackBuild_Scripts.
It's a really good description.

Cheers

atelszewski · 02-23-2008, 02:48 PM

Hi,

Quote:

A build script for VirtualBox is also in the works

I'm interested

Where are you going to put binaries? I mean under /opt or /usr? I know that the output files of vbox build process are quite weird... But also found that, moving *.la under /usr/lib and running ldconfig works, so maybe it is possible to keep files tight and having them under /usr?

Best regards

ppr:kut · 02-24-2008, 02:48 AM

Here it is: http://hw.3kisses.net/sbo/sbo.php

For pulseaudio-support, you'll need the liboil, libatomic_ops and pulseaudio package from the same site.
If you don't want support for it, you can call the build-script like that: "PULSE=no ./virtualbox-ose.SlackBuild"
It uses alienBOB's gcc34 compat packages.

The necessary kernel-module is a separate package, which makes it easier to upgrade to a new kernel.

Quote:

I'm interested Where are you going to put binaries? I mean under /opt or /usr? I know that the output files of vbox build process are quite weird... But also found that, moving *.la under /usr/lib and running ldconfig works, so maybe it is possible to keep files tight and having them under /usr?

You can probably see now yourself

. All the stuff is under /opt/vbox, with links to a wrapper script in /usr/bin.

I'm thankful for any feedback

.
Have fun!

Woodsman · 04-13-2008, 09:38 PM

A few weekends ago I successfully installed VirtualBox 1.5.6. I used the script package from slacky.eu. I had to modify the build script to use GCC 3.4:

--with-gcc=/usr/gcc34/bin/gcc34 \
--with-g++=/usr/gcc34/bin/g++34 \

With that modification the script ran without error. I recommend others who are interested in VirtualBox to try the build package at slacky.eu, which contains all the dependency files too.

I tried to get qemu to work with my new box, but I never got kqemu working. I never had error messages, and info kqemu always showed kqemu running. Yet the on screen response I received indicated the accelerator was not working.

My new box uses an AMD BE-2400, which supports hardware virtualization. Enabling the kvm-amd module was straightforward and VirtualBox uses that module if found. Fast and nice.

I am impressed with the VirtualBox user interface. I don't mind the command line, but I like seeing a well designed interface for those who don't like the command line.

I realize there are front-ends for qemu, but VirtualBox is a joy to experiment with. Very fast on my new box.

Eventually I expect to migrate my Windows box to my new box. I still need to maintain Windows for professional and personal reasons, but VirtualBox will finally allow me to migrate to Slackware as my primary OS and run Windows in a virtual machine.

Many thanks to the slacky.eu community.

atelszewski · 04-17-2008, 05:44 PM

Hi there,
Now I came into some problematic situation, and can't compile vbox anymore

GCC version 3.4 of course, slackware 12 up-to-date. While compiling I get:

Code:

Checking for Qt:
Qt not found at "/usr/lib/qt" or Qt headers not found

And here's some lines from configure.log:

Code:

using the following command line:
g++34 -O -Wall -o .tmp_out .tmp_src.cc -I/usr/lib/qt/include -L/usr/lib/qt/lib -lqt-mt -lpthread
/usr/lib/qt/lib/libqt-mt.so: undefined reference to `__cxa_guard_acquire@CXXABI_1.3'
/usr/lib/qt/lib/libqt-mt.so: undefined reference to `operator delete(void*)@GLIBCXX_3.4'
/usr/lib/qt/lib/libqt-mt.so: undefined reference to `vtable for __cxxabiv1::__si_class_type_info@CXXABI_1.3'

Any ideas?

Best regards,
atelszewski

Woodsman · 04-18-2008, 10:40 PM

On my box /usr/lib/qt is soft linked to qt-3.3.8 (/usr/lib/qt-3.3.8).
Check for that same soft link and check for /usr/lib/qt-3.3.8. If the latter does not exist, you can install the package from the stock Slackware packages. qt-3.3.8 is in the l set of packages.

atelszewski · 04-19-2008, 07:19 AM

Hi,

I've got that link and qt properly installed, and it doesn't help. Furthermore, if I don't pass the gcc location to ./configure, it configures without problems (but gcc version remains 4.x so it will fail to compile). When I pass gcc 3.4 location, then I also need to pass the location of xalan and xerces, even though they are in default locations (/usr/lib). Any ideas?

Best regards,
atelszewski

Woodsman · 04-19-2008, 11:07 AM

Is /usr/gcc34/bin in your path?

ppr:kut · 04-20-2008, 01:42 AM

I did a bit of research on the net. What I found is that it is a gcc issue. Solution posted was to remove all but one gcc but I guess that doesn't count here

. It might be that gcc34 is trying to build with a wrong libstdc++, but this is just a guess. Maybe someone with more insight on such things can help.

Bug report to gentoo with a similar issue: http://bugs.gentoo.org/show_bug.cgi?id=200923
duplicate of: http://bugs.gentoo.org/show_bug.cgi?id=64615

atelszewski · 04-20-2008, 11:28 AM

Hi,

Quote:

Is /usr/gcc34/bin in your path?

Yes, it is (was).

Quote:

Solution posted was to remove all but one gcc but I guess that doesn't count here

Every working solution counts

I removed the GCC 4 and installed GCC 3 from /pasture on Slackware CD. Now compilation fails at this point:

Code:

vfsmod.c:373: error: unknown field `read_inode' specified in initializer

And probably here is the answer. I actually use 2.6.25. Now I'll try to downgrade and see what'll happen. I found that, some binaries were built.

Best regards,
atelszewski

T3slider · 04-20-2008, 12:38 PM

It would probably be easier to setup Slackware 12.0 in a VM, downgrade what is needed there, build a package, and then copy the package to your real setup (just so you won't mess something up -- after all, you're downgrading some major packages here). Just a suggestion though.

ppr:kut · 04-21-2008, 01:20 AM

This sounds like a really cool suggestion

. Problem about it is, that the app he probably uses for such VMs doesn't compile...
( He could use vmware though)