Re: VirtualBox Guest Additions anyone?

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

The saga continues.

One has to use vboxvideo_drv_118.so to get it running, but there was
not corresponding vboxmouse_drv_118.so with the appropriate ABI
version (20), so I had to:
---
--- ./src/VBox/Additions/x11/vboxmouse/Makefile.kmk.ORIG  2017-11-24
10:52:43.234100227 +0000
+++ ./src/VBox/Additions/x11/vboxmouse/Makefile.kmk     2017-11-24
10:53:51.365797901 +0000
@@ -228,6 +228,16 @@
 vboxmouse_drv_112_SOURCES = \
        vboxmouse.c

+DLLS += vboxmouse_drv_118
+vboxmouse_drv_118_TEMPLATE = VBOXGUESTR3XORGMOD
+vboxmouse_drv_118_DEFS := $(vboxmouse_drv_70_DEFS) NO_ANSIC
+vboxmouse_drv_118_INCS := \
+    $(vboxmouse_xorg_INCS) \
+       $(VBOX_PATH_X11_ROOT)/xorg-server-1.18.0 \
+       $(PATH_SUB_CURRENT)
+vboxmouse_drv_118_SOURCES = \
+       vboxmouse.c
+
 endif # neq ($(KBUILD_TARGET),linux)
...

which got me vboxmouse_drv loaded, but now the buttons do not get
passed - basically if you are running xdm and there is an xterm window
to be placed, any mouse click - left, right and middle - moves the
xterm window outline to where the cursor is pointing.

At least we are getting somewhere...

Chavdar



On 23 November 2017 at 22:17, Chavdar Ivanov <ci4ic4%gmail.com@localhost> wrote:
> I needed:
> ...
> --- src/VBox/Runtime/Makefile.kmk.ORIG    2017-11-23 21:41:56.294960546 +0000
> +++ src/VBox/Runtime/Makefile.kmk       2017-11-23 22:14:39.064005844 +0000
> @@ -2435,11 +2435,7 @@
>
>  RuntimeR0Drv_SOURCES.netbsd = \
>         common/misc/thread.cpp \
> -       common/string/memchr.asm \
> -       common/string/memmove.asm \
>         common/string/strpbrk.cpp \
> -       common/string/memcmp.asm \
> -       common/string/strchr.asm \
>         generic/RTAssertShouldPanic-generic.cpp \
>         generic/RTLogWriteDebugger-generic.cpp \
>         generic/RTTimerCreate-generic.cpp \
> ...
>
> and now vboxguest.kmod loads OK.
>
> Chavdar
>
>
> On 23 November 2017 at 19:41, Chavdar Ivanov <ci4ic4%gmail.com@localhost> wrote:
>> The build proceeds with no errors, but when I try to load the module,
>> which I placed in
>>
>>  ls -l /stand/amd64/8.99.7/modules/vboxguest/vboxguest.kmod
>> -r--r--r-- 1 root wheel 280336 Nov 23 19:37
>> /stand/amd64/8.99.7/modules/vboxguest/vboxguest.kmod,
>>
>> I get:
>> kobj_checksyms, 1019: [%M/vboxguest/vboxguest.kmod]: linker error:
>> global symbol `memmove' redefined
>> kobj_checksyms, 1019: [%M/vboxguest/vboxguest.kmod]: linker error:
>> global symbol `memchr' redefined
>> kobj_checksyms, 1019: [%M/vboxguest/vboxguest.kmod]: linker error:
>> global symbol `memcmp' redefined
>> kobj_checksyms, 1019: [%M/vboxguest/vboxguest.kmod]: linker error:
>> global symbol `strchr' redefined
>>
>> No idea... Perhaps some mod in the NetBSD specific build instructions.
>>
>> Chavdar
>>
>> On 21 November 2017 at 23:48, Valery Ushakov <uwe%stderr.spb.ru@localhost> wrote:
>>> On Tue, Nov 21, 2017 at 21:14:55 +0000, Chavdar Ivanov wrote:
>>>
>>>> with which I was able to carry on building VirtualBox 5.1.30 much further.
>>>> It stopped eventually:
>>>> ..
>>>> Build: Compiling ServicesR0 -
>>>
>>> Oh, sorry, I forgot to provide the build instructions for the guest
>>> additions.  You ended up building not the GAs but vbox itself, which
>>> doesn't support netbsd as a host.
>>>
>>> You need to install devel/yasm
>>>
>>> You need to create the file LocalConfig.kmk in the top-level directory
>>> with something like this:
>>>
>>> ----8<--------8<----
>>> # Where the NetBSD sources are
>>> # VBOX_NETBSD_SRC := /usr/src
>>>
>>> # If you build the same workspace on multiple NetBSD versions (amd64
>>> # vs i386 is taken care of by the build system)
>>> # PATH_OUT_BASE := $(PATH_ROOT)/out-$(shell uname -r)
>>>
>>> # XXX: svn checkout on my host is done with an old svn version that
>>> # svn in the netbsd guest is not happy about, so proivde the revision
>>> # manually
>>> # VBOX_SVN_REV := 9999
>>>
>>> # XXX: I don't remember if that affects GAs
>>> # VBOX_WITHOUT_HARDENING := 1
>>>
>>> VBOX_ONLY_ADDITIONS := 1
>>> VBOX_WITH_ADDITION_DRIVERS := 1
>>> VBOX_WITH_X11_ADDITIONS := 1
>>> ----8<--------8<----
>>>
>>>
>>> After that you should be able to build with:
>>>
>>>   kmk KBUILD_VERBOSE=2 BUILD_TYPE=release   # or BUILD_TYPE=debug
>>>
>>>
>>> PS: And if someone feels like hacking on shared folders or drm/kms
>>> driver, drop me a mail.
>>>
>>> -uwe
>>
>>
>>
>> --
>> ----
>
>
>
> --
> ----



-- 
----