> On 26 Feb 2017, at 14:42, Harry Putnam <[email protected]> wrote:
>
> My biggest trouble is that I just don't see anything looking like a
> clue that I recognize as such.... in those logs.
I always search for "error", and look around the first one.
I'd have assumed subsequent errors would be a result of the first one.
Early in the log you sent there are a couple of entries like this:
Checking for libvpx:
vpx not found at -lvpx or vpx headers not found
Check the file
/var/tmp/portage/app-emulation/virtualbox-guest-additions-5.1.14/work/VirtualBox-5.1.14/configure.log
for detailed error information.
But then the emerge continues for many hundreds of lines more, apparently
unaffected.
I would google the "vpx not found…" line and see if I get any hints, but I
don't feel that's important - I think it may just be a warning.
The string "error" comes up a couple of times in the context of -Werror
compiler flags, but that's clearly not what we're looking for.
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; \
Interestingly, I see the mess of colour code brackets and numbers when I open
the log you attached in TextEdit, vim or my Mac's Console.app logfile viewer.
If cat or sed them into the terminal (I noticed this adding the embedding
spaces to the above) the colour codes are converted to colours and the text is
displayed nicely.
In the above the filenames and the "‘union atomic_read(const
atomic_t*)::<anonymous>’" are bold white, and the word "error:" is displayed in
red.
Stroller.
