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?
>
> 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.
>
> Cheers,
> Wol
