On 1/1/23 11:14, Wols Lists wrote:
> On 01/01/2023 18:33, cal wrote:
>> On 1/1/23 03:07, Wols Lists wrote:
>>> I got the following build failure in my weekly emerge yesterday ...
>>>
>>> * Messages for package mail-client/thunderbird-102.6.0:
>>>
>>> * ERROR: mail-client/thunderbird-102.6.0::gentoo failed (compile
>>> phase):
>>> * (no error message)
>>> *
>>> * Call stack:
>>> * ebuild.sh, line 136: Called src_compile
>>> * environment, line 4782: Called die
>>> * The specific snippet of code:
>>> * ${virtx_cmd} ./mach build --verbose || die
>>> *
>>> * If you need support, post the output of `emerge --info
>>> '=mail-client/thunderbird-102.6.0::gentoo'`,
>>> * the complete build log and the output of `emerge -pqv
>>> '=mail-client/thunderbird-102.6.0::gentoo'`.
>>> * The complete build log is located at
>>> '/var/tmp/portage/mail-client/thunderbird-102.6.0/temp/build.log'.
>>> * The ebuild environment file is located at
>>> '/var/tmp/portage/mail-client/thunderbird-102.6.0/temp/environment'.
>>> * Working directory:
>>> '/var/tmp/portage/mail-client/thunderbird-102.6.0/work/thunderbird-102.6.0'
>>> * S:
>>> '/var/tmp/portage/mail-client/thunderbird-102.6.0/work/thunderbird-102.6.0'
>
>> Can you post the outputs referenced above/the full build log and your
>> portage configuration?
>
> Files attached - not sure it's everything you want, but I'm sure you'll
> let me know if I've messed up ... :-)
If you scroll up a bit in build.log, you can see that clang has crashed:
[...]
836:17.68 clang-15: error: clang frontend command failed with exit code
139 (use -v to see invocation)
836:17.68 clang version 15.0.6
836:17.68 Target: x86_64-pc-linux-gnu
836:17.69 Thread model: posix
836:17.69 InstalledDir: /usr/lib/llvm/15/bin
836:17.69 Configuration file: /etc/clang/clang++.cfg
836:18.07 clang-15: note: diagnostic msg:
836:18.07 ********************
836:18.07 PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
836:18.07 Preprocessed source(s) and associated run script(s) are
located at:
836:18.07 clang-15: note: diagnostic msg:
/var/tmp/portage/mail-client/thunderbird-102.6.0/temp/Unified_cpp_dom_media_webaudio1-f85814.cpp
836:18.07 clang-15: note: diagnostic msg:
/var/tmp/portage/mail-client/thunderbird-102.6.0/temp/Unified_cpp_dom_media_webaudio1-f85814.sh
836:18.07 clang-15: note: diagnostic msg:
836:18.07 ********************
If you search for "clang frontend command failed with exit code 139" it
turns up a few GitHub issues which may or may not be related; you may
wish to follow up with upstream on that.
FWIW, Thunderbird builds fine with GCC on my machine -- I'm unsure of
your reasons for setting your Portage compiler to clang, but you may
wish to use a package.env override to build Thunderbird with GCC as a
workaround until the problem can be fixed upstream.
>>>
>>> I'm wondering whether this will simply clear itself next week, seeing as
>>> last week I got a very similar failure for both thunderbird and firefox.
>>>
>>> Could it simply be a bit of the fallout from app-alternatives? Of
>>> course, it's blocking my depclean ...
>> Having followed this list for quite a while, my first guess whenever
>> someone fails to compile a web browser or similar heavy piece of
>> software (I'm counting Thunderbird here) is that they ran out of memory.
>> I would double check your MAKEOPTS and RAM size and try building with a
>> smaller -j. But as noted above, perhaps if you attach the full build
>> log for Thunderbird, a more obvious cause will appear in the output.
>>>
>
> thewolery /usr/local # df
> Filesystem 1K-blocks Used Available Use%
> Mounted on
> none 16404256 3328 16400928 1% /run
> udev 10240 0 10240 0% /dev
> tmpfs 16404256 0 16404256 0%
> /dev/shm
> /dev/dm-1 131001348 101620580 22653500 82% /
> tmpfs 16404260 4 16404256 1% /tmp
> /dev/mapper/vg--home-lv--data 2064042928 1472050236 487118712 76% /home
> tmpfs 3280848 56 3280792 1%
> /run/user/1000
> /dev/mapper/vg--home-lv--Videos 772966856 276285468 457343404 38%
> /home/Videos
> /dev/mapper/vg--home-lv--ISO 153707984 88546712 57280568 61%
> /home/ISO
> thewolery /usr/local #
>
> There's 28GB free disk space, surely that's enough? And iirc this
> machine has 32GB ram. Or do I need to do a bit of a clean-out - I appear
> to have used some 100GB for root which seems rather a lot ...
>
> Cheers,
> Wol
