Stroller <strol...@stellar.eclipse.co.uk> writes:

[...]

> I would be looking primarily at the next point the word "error" comes up 
> properly, which is here: 
>
>     from 
> /var/tmp/portage/app-emulation/virtualbox-guest-additions-5.1.14/work/VirtualBox-5.1.14/src/VBox/Runtime/common/alloc/alloc.cpp:34:
>     /lib/modules/4.9.10-gentoo/build/arch/x86/include/asm/atomic.h: In 
> function ‘int atomic_read(const atomic_t*)’:
>     /lib/modules/4.9.10-gentoo/build/include/linux/compiler.h:305:42: error: 
> uninitialized const member in ‘union atomic_read(const 
> atomic_t*)::<anonymous>’
>       union { typeof(x) __val; char __c[1]; } __u;   \


First off, thanks for the leg work on this.

Using search terms from your finding:
I did find something that might make some difference on the error you
found (above).

https://bugs.gentoo.org/show_bug.cgi?id=603472

It is a bug already on the bug setup... and one of the heavy hitters
there has this to say:

"Lars Wendler (Polynomial-C)  gentoo-dev 2017-02-08 15:44:54 UTC
This is an issue that - according to upstream - will not be fixed anytime soon.
So I suggest to use 4.4 LTS kernel for Gentoo guests VMs for the time being."

Maybe if I backed up to a 4.4 kernel I'd have better luck.

However, I can report that if USER reinstalls the standard vbox
guest-additions that come with each release of vbox (It can be
initiated by the `Devices' menu on the vbox interface (last item =
Insert Guest additions into cdrom )). (And does it enough times) It
seems to work thereafter, (the needed module is present) assuming that
installation finishes with no errors.

After wards I saw the glad tidings:

reader > sudo lsmod
Module                  Size  Used by
vboxvideo              36795  2
vboxguest             201560  4 vboxvideo
ttm                    69735  1 vboxvideo

It seems to matter when you install the vbox [not from portage]
guest-additions because I did so several times during my efforts to
get X working.  Finally it made a difference.

You are expected to re-install them after any kernel build but I did
that as well and still it only worked after a certain point... maybe
once I managed to get enough stuff installed from emerge.

So, to summarize  It appears you are not likely to get things working
with too new a kernel but can possibly fall back on repeated
reinstalls of the vbox guest-additions.

In my case I've succesfully built a 4.9.10 kernel and managed to get X
working even though two virtual-box packages from portage failed to
build
   x11-drivers/xf86-video-virtualbox-5.1.14
   app-emulations/virtualbox-guest-additionsvirtualbox-guest-additions

So, I've got X up and successfully installed my desktop of choice
lxde.  Things are looking up.


Reply via email to