1 |
On Monday 27 Feb 2017 10:09:34 Harry Putnam wrote: |
2 |
|
3 |
> I guess I'll try this once more... Its still a big log but I cleaned |
4 |
> up the escapes ... it is a fresh try at building |
5 |
> xf86-video-virtualbox-5.1.14 |
6 |
> |
7 |
> Still failing in the same way and still not seeing clues in the |
8 |
> log... probably my own fault. |
9 |
|
10 |
I see this, starting at line 3324 in your newly attached log: |
11 |
|
12 |
In file included from /var/tmp/portage/x11-drivers/xf86-video- |
13 |
virtualbox-5.1.14/work/VirtualBox-5.1.14/include/iprt/types.h:140:0, |
14 |
from /var/tmp/portage/x11-drivers/xf86-video- |
15 |
virtualbox-5.1.14/work/VirtualBox-5.1.14/include/iprt/mem.h:31, |
16 |
from /var/tmp/portage/x11-drivers/xf86-video- |
17 |
virtualbox-5.1.14/work/VirtualBox-5.1.14/src/VBox/Runtime/common/alloc/alloc.cpp:34: |
18 |
/lib/modules/4.9.10-gentoo/build/arch/x86/include/asm/atomic.h: In function |
19 |
‘int atomic_read(const atomic_t*)’: |
20 |
/lib/modules/4.9.10-gentoo/build/include/linux/compiler.h:305:42: error: |
21 |
uninitialized const member in ‘union atomic_read(const |
22 |
atomic_t*)::<anonymous>’ |
23 |
union { typeof(x) __val; char __c[1]; } __u; \ |
24 |
|
25 |
That's similar to what Stroller found the first time, just not quite the |
26 |
same. It looks like a code error in VirtualBox, but it can't be because I've |
27 |
compiled that version here with no trouble. That means something is awry in |
28 |
your setup. |
29 |
|
30 |
Have you tried setting -j1? I ask because it looks as though components are |
31 |
being compiled in a different order from the last time. |
32 |
|
33 |
If I have a useful suggestion after some time for thought, I'll offer it |
34 |
then. |
35 |
|
36 |
-- |
37 |
Regards |
38 |
Peter |