On Monday 27 Feb 2017 10:09:34 Harry Putnam wrote:
> I guess I'll try this once more... Its still a big log but I cleaned
> up the escapes ... it is a fresh try at building
> xf86-video-virtualbox-5.1.14
>
> Still failing in the same way and still not seeing clues in the
> log... probably my own fault.
I see this, starting at line 3324 in your newly attached log:
In file included from /var/tmp/portage/x11-drivers/xf86-video-
virtualbox-5.1.14/work/VirtualBox-5.1.14/include/iprt/types.h:140:0,
from /var/tmp/portage/x11-drivers/xf86-video-
virtualbox-5.1.14/work/VirtualBox-5.1.14/include/iprt/mem.h:31,
from /var/tmp/portage/x11-drivers/xf86-video-
virtualbox-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; \
That's similar to what Stroller found the first time, just not quite the
same. It looks like a code error in VirtualBox, but it can't be because I've
compiled that version here with no trouble. That means something is awry in
your setup.
Have you tried setting -j1? I ask because it looks as though components are
being compiled in a different order from the last time.
If I have a useful suggestion after some time for thought, I'll offer it
then.
--
Regards
Peter
