LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-31-2018, 05:25 AM   #1
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 548

Rep: Reputation: 57
Can't compile virtualbox-kernel-addons


Bit behind the curve on keeping my current (aka Slackware 15.0) development platform that runs in VirtualBox up to date.

On one of my production boxes (Slackware 14.2) I run VirtualBox (5.0.40) installed from SlackBuilds.org.

In the VirtualBox client after upgrading the linux kernel I rebuild virtualbox-kernel-addons and virtualbox-addons sometimes after certain upgrades this fails and I have to go digging around for the fix.

A few days ago I upgraded from kernel 4.14.71 to 4.19.12. When I try to rebuild virtualbox-kernel-addons I get these errors

Quote:
/tmp/SBo/virtualbox-kernel-addons/vboxsf/utils.c: In function ‘sf_init_inode’:
/tmp/SBo/virtualbox-kernel-addons/vboxsf/utils.c:165:28: error: passing argument 1 of ‘sf_ftime_from_timespec’ from incompatible pointer type [-Werror=incompatible-pointer-types]
sf_ftime_from_timespec(&inode->i_atime, &info->AccessTime);
^~~~~~~~~~~~~~~
/tmp/SBo/virtualbox-kernel-addons/vboxsf/utils.c:53:53: note: expected ‘struct timespec *’ but argument is of type ‘struct timespec64 *’
static void sf_ftime_from_timespec(struct timespec *tv, RTTIMESPEC *ts)
~~~~~~~~~~~~~~~~~^~
/tmp/SBo/virtualbox-kernel-addons/vboxsf/utils.c:166:28: error: passing argument 1 of ‘sf_ftime_from_timespec’ from incompatible pointer type [-Werror=incompatible-pointer-types]
sf_ftime_from_timespec(&inode->i_ctime, &info->ChangeTime);
^~~~~~~~~~~~~~~
/tmp/SBo/virtualbox-kernel-addons/vboxsf/utils.c:53:53: note: expected ‘struct timespec *’ but argument is of type ‘struct timespec64 *’
static void sf_ftime_from_timespec(struct timespec *tv, RTTIMESPEC *ts)
~~~~~~~~~~~~~~~~~^~
/tmp/SBo/virtualbox-kernel-addons/vboxsf/utils.c:167:28: error: passing argument 1 of ‘sf_ftime_from_timespec’ from incompatible pointer type [-Werror=incompatible-pointer-types]
sf_ftime_from_timespec(&inode->i_mtime, &info->ModificationTime);
^~~~~~~~~~~~~~~
/tmp/SBo/virtualbox-kernel-addons/vboxsf/utils.c:53:53: note: expected ‘struct timespec *’ but argument is of type ‘struct timespec64 *’
static void sf_ftime_from_timespec(struct timespec *tv, RTTIMESPEC *ts)
~~~~~~~~~~~~~~~~~^~
/tmp/SBo/virtualbox-kernel-addons/vboxsf/utils.c: In function ‘sf_setattr’:
/tmp/SBo/virtualbox-kernel-addons/vboxsf/utils.c:377:54: error: passing argument 2 of ‘sf_timespec_from_ftime’ from incompatible pointer type [-Werror=incompatible-pointer-types]
sf_timespec_from_ftime(&info.AccessTime, &iattr->ia_atime);
^~~~~~~~~~~~~~~~
/tmp/SBo/virtualbox-kernel-addons/vboxsf/utils.c:63:69: note: expected ‘struct timespec *’ but argument is of type ‘struct timespec64 *’
static void sf_timespec_from_ftime(RTTIMESPEC *ts, struct timespec *tv)
~~~~~~~~~~~~~~~~~^~
/tmp/SBo/virtualbox-kernel-addons/vboxsf/utils.c:379:60: error: passing argument 2 of ‘sf_timespec_from_ftime’ from incompatible pointer type [-Werror=incompatible-pointer-types]
sf_timespec_from_ftime(&info.ModificationTime, &iattr->ia_mtime);
^~~~~~~~~~~~~~~~
/tmp/SBo/virtualbox-kernel-addons/vboxsf/utils.c:63:69: note: expected ‘struct timespec *’ but argument is of type ‘struct timespec64 *’
static void sf_timespec_from_ftime(RTTIMESPEC *ts, struct timespec *tv)
~~~~~~~~~~~~~~~~~^~
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:303: /tmp/SBo/virtualbox-kernel-addons/vboxsf/utils.o] Error 1
make[1]: *** [Makefile:1517: _module_/tmp/SBo/virtualbox-kernel-addons/vboxsf] Error 2
make[1]: Leaving directory '/usr/src/linux-4.19.13'
make: *** [/tmp/SBo/virtualbox-kernel-addons/vboxsf/Makefile.include.footer:101: vboxsf] Error 2

I'm using the SlackBuild from https://github.com/Ponce/slackbuilds.git

When I last successfully compiled virtualbox-kernel-addons I was using virtualbox-kernel-addons-5.2.8.tar.xz

I've tried virtualbox-kernel-addons-5.2.10.tar.xz also get the same failure.

Both of these files were obtained from http://www.liwjatan.at/files/src/vir...kernel-addons/

This morning I've upgraded my VirtualBox client to linux kernel 4.19.13.

Have found reference to a failure on the virtualbox forum https://forums.virtualbox.org/viewtopic.php?f=3&t=89455 that seems to be similar to the problem I'm getting.

Not sure how to progress to a solution yet, which is why I'm raising it here.

Wishing everyone a happy New Year.

Alex

Last edited by aikempshall; 12-31-2018 at 05:26 AM. Reason: Wrong title
 
Old 12-31-2018, 05:37 AM   #2
Qury
Member
 
Registered: Feb 2004
Location: Dublin
Distribution: Slackware
Posts: 151

Rep: Reputation: 136Reputation: 136
Hi Alex

I have current with kernel 4.19.13 working in virtualbox 5.22 but i had to install the guest additions from Virtualbox 6.x

You can download the guest additions iso from the virtualbox website.
 
Old 12-31-2018, 10:41 AM   #3
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 548

Original Poster
Rep: Reputation: 57
Thanks for Qury for the reply.



Quote:
You can download the guest additions iso from the virtualbox website.
I've downloaded VBoxGuestAdditions_6.0.0.iso, mounted it and ran VBoxLinuxAdditions.run as root.

It wasn't successful

Quote:
Error building the module. Build output follows.
make V=1 CONFIG_MODULE_SIG= -C /lib/modules/4.19.13/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j4 modules
make[1]: warning: -jN forced in submake: disabling jobserver mode.
arch/x86/Makefile:150: CONFIG_X86_X32 enabled but no binutils support
test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
echo >&2; \
echo >&2 " ERROR: Kernel configuration is invalid."; \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo >&2 ; \
/bin/false)
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
make -f ./scripts/Makefile.build obj=/tmp/vbox.0
(cat /dev/null; echo kernel//tmp/vbox.0/vboxguest.ko > /tmp/vbox.0/modules.order
gcc -Wp,-MD,/tmp/vbox.0/.VBoxGuest.o.d -nostdinc -isystem /usr/lib64/gcc/x86_64-slackware-linux/8.2.0/include -I./arch/x86/include -I./arch/x86/include/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -DCC_HAVE_ASM_GOTO -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -O2 -fstack-protector-strong -pg -Wno-declaration-after-statement -include /tmp/vbox.0/include/VBox/VBoxGuestMangling.h -fno-pie -I/lib/modules/4.19.13/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -I/tmp/vbox.0/vboxguest/ -I/tmp/vbox.0/vboxguest/include -I/tmp/vbox.0/vboxguest/r0drv/linux -D__KERNEL__ -DMODULE -DVBOX -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_GUEST -DIN_GUEST_R0 -DIN_MODULE -DRT_WITH_VBOX -DVBGL_VBOXGUEST -DVBOX_WITH_HGCM -DRT_ARCH_AMD64 -DVBOX_WITH_64_BITS_GUESTS -DMODULE -DKBUILD_BASENAME='"VBoxGuest"' -DKBUILD_MODNAME='"vboxguest"' -c -o /tmp/vbox.0/VBoxGuest.o /tmp/vbox.0/VBoxGuest.c
gcc -Wp,-MD,/tmp/vbox.0/.VBoxGuestR0LibHGCMInternal.o.d -nostdinc -isystem /usr/lib64/gcc/x86_64-slackware-linux/8.2.0/include -I./arch/x86/include -I./arch/x86/include/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -DCC_HAVE_ASM_GOTO -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -O2 -fstack-protector-strong -pg -Wno-declaration-after-statement -include /tmp/vbox.0/include/VBox/VBoxGuestMangling.h -fno-pie -I/lib/modules/4.19.13/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -I/tmp/vbox.0/vboxguest/ -I/tmp/vbox.0/vboxguest/include -I/tmp/vbox.0/vboxguest/r0drv/linux -D__KERNEL__ -DMODULE -DVBOX -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_GUEST -DIN_GUEST_R0 -DIN_MODULE -DRT_WITH_VBOX -DVBGL_VBOXGUEST -DVBOX_WITH_HGCM -DRT_ARCH_AMD64 -DVBOX_WITH_64_BITS_GUESTS -DMODULE -DKBUILD_BASENAME='"VBoxGuestR0LibHGCMInternal"' -DKBUILD_MODNAME='"vboxguest"' -c -o /tmp/vbox.0/VBoxGuestR0LibHGCMInternal.o /tmp/vbox.0/VBoxGuestR0LibHGCMInternal.c
gcc -Wp,-MD,/tmp/vbox.0/.VBoxGuestR0LibGenericRequest.o.d -nostdinc -isystem /usr/lib64/gcc/x86_64-slackware-linux/8.2.0/include -I./arch/x86/include -I./arch/x86/include/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -DCC_HAVE_ASM_GOTO -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -O2 -fstack-protector-strong -pg -Wno-declaration-after-statement -include /tmp/vbox.0/include/VBox/VBoxGuestMangling.h -fno-pie -I/lib/modules/4.19.13/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -I/tmp/vbox.0/vboxguest/ -I/tmp/vbox.0/vboxguest/include -I/tmp/vbox.0/vboxguest/r0drv/linux -D__KERNEL__ -DMODULE -DVBOX -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_GUEST -DIN_GUEST_R0 -DIN_MODULE -DRT_WITH_VBOX -DVBGL_VBOXGUEST -DVBOX_WITH_HGCM -DRT_ARCH_AMD64 -DVBOX_WITH_64_BITS_GUESTS -DMODULE -DKBUILD_BASENAME='"VBoxGuestR0LibGenericRequest"' -DKBUILD_MODNAME='"vboxguest"' -c -o /tmp/vbox.0/VBoxGuestR0LibGenericRequest.o /tmp/vbox.0/VBoxGuestR0LibGenericRequest.c
gcc -Wp,-MD,/tmp/vbox.0/.VBoxGuest-linux.o.d -nostdinc -isystem /usr/lib64/gcc/x86_64-slackware-linux/8.2.0/include -I./arch/x86/include -I./arch/x86/include/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -DCC_HAVE_ASM_GOTO -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -O2 -fstack-protector-strong -pg -Wno-declaration-after-statement -include /tmp/vbox.0/include/VBox/VBoxGuestMangling.h -fno-pie -I/lib/modules/4.19.13/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -I/tmp/vbox.0/vboxguest/ -I/tmp/vbox.0/vboxguest/include -I/tmp/vbox.0/vboxguest/r0drv/linux -D__KERNEL__ -DMODULE -DVBOX -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_GUEST -DIN_GUEST_R0 -DIN_MODULE -DRT_WITH_VBOX -DVBGL_VBOXGUEST -DVBOX_WITH_HGCM -DRT_ARCH_AMD64 -DVBOX_WITH_64_BITS_GUESTS -DMODULE -DKBUILD_BASENAME='"VBoxGuest_linux"' -DKBUILD_MODNAME='"vboxguest"' -c -o /tmp/vbox.0/VBoxGuest-linux.o /tmp/vbox.0/VBoxGuest-linux.c
cc1: error: code model �<80><98>kernel�<80><99> not supported in the 32 bit mode
cc1: error: code model �<80><98>kernel�<80><99> not supported in the 32 bit mode
make[2]: *** [scripts/Makefile.build:303: /tmp/vbox.0/VBoxGuestR0LibHGCMInternal.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [scripts/Makefile.build:303: /tmp/vbox.0/VBoxGuest.o] Error 1
cc1: error: code model �<80><98>kernel�<80><99> not supported in the 32 bit mode
cc1: error: code model �<80><98>kernel�<80><99> not supported in the 32 bit mode
make[2]: *** [scripts/Makefile.build:303: /tmp/vbox.0/VBoxGuestR0LibGenericRequest.o] Error 1
make[2]: *** [scripts/Makefile.build:303: /tmp/vbox.0/VBoxGuest-linux.o] Error 1
make[1]: *** [Makefile:1517: _module_/tmp/vbox.0] Error 2
make: *** [/tmp/vbox.0/Makefile.include.footer:106: vboxguest] Error 2


I think I might call it quits for this year. Go out and celebrate. I'm sure everything will be a lot clearer when I return on Wednesday!
 
Old 12-31-2018, 11:45 AM   #4
solarfields
Member
 
Registered: Feb 2006
Location: Outer Shpongolia
Distribution: Slackware
Posts: 926

Rep: Reputation: 463Reputation: 463Reputation: 463Reputation: 463Reputation: 463
just install VirtualBox on your host from the *.run file provided by Oracle and then insert the guest additions 'disc' in the virtual machine...
 
Old 12-31-2018, 11:53 AM   #5
upnort
Member
 
Registered: Oct 2014
Distribution: Slackware, Proxmox, Debian, CentOS, Ubuntu MATE
Posts: 804

Rep: Reputation: Disabled
I'm running Current in VBox. The GA are needed only if shared folder support (vboxsf) is desired. Otherwise the kernel already supports vboxguest and vboxvideo natively.

VBox 5.0.40 has not been supported upstream in a long time. Compiling 5.2 requires minor tweaks to the build script.

I am running 5.2.22. I haven't paid close attention, but I think a VM full reboot is needed before attempting to install the GA. I am using the 5.2.22 GA ISO.
 
Old 01-01-2019, 04:35 PM   #6
clavisound
LQ Newbie
 
Registered: Apr 2011
Posts: 15

Rep: Reputation: 1
I am not sure, but maybe the kernel source tree is the problem? I had the same problem on my host.

Today I had experienced the same problem with the guest.

I think here is the full explanation. In my case the compile went fine, but the installation was on wrong folder (/lib/modules/version vs /lib/modules/version-smp)

I did this for the guest.
Code:
cd /usr/src/linux
cp /boot/config .config
make clean
make modules_prepare
cd /opt/VBoxGuestAdditionsBlah-Blah/src/vboxguest-blah-blah
make install
depmod -a
modprobe vboxguest
modprobe vboxvideo
modprobe vboxsf
et voila!

Last edited by clavisound; 01-01-2019 at 04:37 PM.
 
Old 01-01-2019, 07:04 PM   #7
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,561
Blog Entries: 3

Rep: Reputation: 442Reputation: 442Reputation: 442Reputation: 442Reputation: 442
You could save your self a ton of work just install the latest 5.XXX not the 6.00 install it the way the developers built it.
Host is your computer the guest is the system running in virtualbox.
then down load the guest-extension-iso and use it in your guest.

that is the best way if your running current it will rebuild per kernel at reboot.
stop beating that dead horse 7 years ago.
VirtualBox Graphical User Interface
Version 5.2.22 r126460 (Qt5.6.1)
uname -r
4.19.13
Slackware 14.2+

Last edited by Drakeo; 01-01-2019 at 07:08 PM.
 
Old 01-01-2019, 07:10 PM   #8
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,561
Blog Entries: 3

Rep: Reputation: 442Reputation: 442Reputation: 442Reputation: 442Reputation: 442
as you know Slackware current 14.2+ does not use qt5. this is why you need so use there installer with there static libs.
have fun building anything that requires qt5 in 14.2+
 
Old 01-02-2019, 04:35 AM   #9
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 548

Original Poster
Rep: Reputation: 57
I have 8 virtualbox clients of which three are Slackware 14.2 clients and one is a Slackware 14.2+ client.

The host is 14.2 running virtualbox 5.0.40.

When I upgraded 14.2+ I with the 4.19.12 I got the kde logon screen and enter the password, but it didn't appear to respond to the <enter> key. I could log in as single user non graphical mode. Upgraded to 4.19.13 could now log in kde.

Couldn't get shared folders mount.vboxsf wasn't working neither could I get full screen.

Tried compiling VirtualBox addons 5.8 got the errors described in my initial post. Subsequently noticed that I was compiling using 32bit gcc, so removed the 32dev scripts from /etc/profiles.d.

I've now successfully compiled virtualbox, virtualbox-addons, virtualbox-kernel and virtualbox-kernel-addons for 6.0.0 on my Slackware 14.2+ virtualbox guest.

Now I can mount the shared folders, but still can't get full screen.

So work in progress.
 
Old 01-02-2019, 04:39 AM   #10
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 548

Original Poster
Rep: Reputation: 57
Quote:
Originally Posted by Drakeo View Post
You could save your self a ton of work just install the latest 5.XXX not the 6.00 install it the way the developers built it.
Host is your computer the guest is the system running in virtualbox.
then down load the guest-extension-iso and use it in your guest.

that is the best way if your running current it will rebuild per kernel at reboot.
stop beating that dead horse 7 years ago.
VirtualBox Graphical User Interface
Version 5.2.22 r126460 (Qt5.6.1)
uname -r
4.19.13
Slackware 14.2+

Drakeo are you suggesting that I upgrade my host (14.2) to VirtualBox 5.2.22 and my 14.2+ client to 5.2.22 as well?
 
Old 01-02-2019, 07:55 AM   #11
ludist
Member
 
Registered: Nov 2005
Location: Greece
Distribution: Slackware
Posts: 135

Rep: Reputation: 17
Quote:
Originally Posted by aikempshall View Post
Drakeo are you suggesting that I upgrade my host (14.2) to VirtualBox 5.2.22 and my 14.2+ client to 5.2.22 as well?
I think you are confused. Host has the VirtualBox, guest has nothing, only Guest Additions if you want. In closed source version it's already added in host in a file /opt/VirtuaBol/additions/VBoxGuestAdditions.iso to be installed in the guest.

In my setup, the guest auto-compiles the GA from above .iso.

Mind you, I use the close source version from here, never had problems. Not the slackware way, but I suppose the compile time is too much for VirtualBox. But my main reason was the extpack and more simple to install the closed source.

I just checked in SBo and I see that you have to specify kernel version to build the GA. Did you do that?
 
Old 01-02-2019, 09:17 AM   #12
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 548

Original Poster
Rep: Reputation: 57
Quote:
Originally Posted by ludist View Post
I think you are confused. Host has the VirtualBox, guest has nothing, only Guest Additions if you want. In closed source version it's already added in host in a file /opt/VirtuaBol/additions/VBoxGuestAdditions.iso to be installed in the guest.

In my setup, the guest auto-compiles the GA from above .iso.

Mind you, I use the close source version from here, never had problems. Not the slackware way, but I suppose the compile time is too much for VirtualBox. But my main reason was the extpack and more simple to install the closed source.

I just checked in SBo and I see that you have to specify kernel version to build the GA. Did you do that?
I don't think I'm confused. Might just have not explained myself very well.

My host is Slackware 14.2 with VirtualBox 5.0.40. I built within one of my guests, which happened to be running 14.2+, virtualbox 6.0.0 and virtualbox-kernel 6.0.0. I then used virtualbox-kernel-mksrctarball.sh and virtualbox-kernel-addons-mksrctarball.sh to make the source files to build virtualbox-kernel-addons and virtualbox-addons.


Before doing the above I had a go with GA, but by then I'd already rebooted so didn't have to supply the new kernel version number to build the GA.

I think I'm almost there in that I can -
  1. mount shared drives using
    Code:
    mount -t vboxsf -o uid=1001,gid=100 Documents /home/alex/Documents
  2. copy and paste between host and client

The only thing that's not working is full screen.
 
Old 01-02-2019, 12:33 PM   #13
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,561
Blog Entries: 3

Rep: Reputation: 442Reputation: 442Reputation: 442Reputation: 442Reputation: 442
what I am saying is the virtualbox devs have made it for use with Slacware in mind a long time ago.
and at this time. In the world of Slackware that is designed to run programs as the developers wanted them it will not hurt.
they build it static not to hurt your system and allows you to uninstall as needed.
keep your little virtual drives it will be picked up.

I gave up dealling with building the stuff designed to be built by another system.

six is still beta and broken.
https://download.virtualbox.org/virtualbox/

I would uninstall the packages you have built and installed.
grab the latest stable
https://download.virtualbox.org/virtualbox/5.2.22/
x86_64
https://download.virtualbox.org/virt...inux_amd64.run

as root
sh VirtualBox-5.2.22-126460-Linux_amd64.run
after it is installed boot your guest system
then insert this Iso

https://download.virtualbox.org/virt...ons_5.2.22.iso
open the iso image as a cdrom. and run the script.
reboot your guest system.
set bidirectional for clipboard and drop and drag.
set you shared folder.
you get that far it is easy to mount your shared folder.
it is already mounted you just need to make sure you have a link to it and the vboxsf is loaded.

Last edited by Drakeo; 01-02-2019 at 12:35 PM.
 
Old 01-02-2019, 06:43 PM   #14
Qury
Member
 
Registered: Feb 2004
Location: Dublin
Distribution: Slackware
Posts: 151

Rep: Reputation: 136Reputation: 136
Hi,

Here is my step by step instructions:
Code:
cd /usr/local/src
wget https://www.virtualbox.org/download/testcase/VBoxGuestAdditions_6.0.1-127639.iso
mount -t iso9660 -o loop VBoxGuestAdditions_6.0.1-127639.iso /mnt/cdrom/
cd /mnt/cdrom
./VBoxLinuxAdditions.run --keep --target /tmp/VBOX
# the above will fail, but go to /tmp/VBOX to build and install the kernel modules
cd /tmp/VBOX
tar -xf VBoxGuestAdditions-amd64.tar.bz2
cd /tmp/VBOX/src/vboxguest-6.0.0
make
make install
 
Old 01-03-2019, 07:36 AM   #15
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 924

Rep: Reputation: 353Reputation: 353Reputation: 353Reputation: 353
Quote:
Originally Posted by Drakeo View Post
six is still beta and broken.
https://download.virtualbox.org/virtualbox/
Quote:
December 18th, 2018. VirtualBox 6.0 released! Oracle today released a new major release of VirtualBox. See the Changelog for details.
https://www.virtualbox.org/

It's not broken, working fine here. Installed on my system December 19th using the installer provided by VirtualBox. Using with several versions of Slackware, Mint, MX Linux and Windows 7.

From the page you linked, LATEST indicates 6.0.0.

Last edited by chrisretusn; 01-03-2019 at 07:38 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Can't compile virtualbox-addons with gcc 8.2.0 aikempshall Slackware 3 08-11-2018 04:26 AM
Does Deepin Desktop Environment support addons that can heavily modify the desktop environment? Joe232 Linux - Software 1 02-07-2018 08:43 AM
Can't download addons Firefox 2.0.04 Suse 10.2 vladi4az Linux - Newbie 1 06-15-2007 11:27 PM
ipcop addons rtr Linux - Security 1 12-10-2003 11:43 AM
RADIO / TV TUNER ADDONS Stephanie Linux - General 3 05-11-2001 01:57 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:00 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration