firefox 128 can not be compiled

[st834]

Hello, an error occurs when building firefox 128.4.0. i have now received my compilation output:

>>> Failed to emerge www-client/firefox-128.4.0, Log file:

>>> '/var/tmp/portage/www-client/firefox-128.4.0/temp/build.log'

* Messages for package www-client/firefox-128.4.0:

* ERROR: www-client/firefox-128.4.0::gentoo failed (compile phase):
* Failed to run './mach build --verbose'
*
* Call stack:
* ebuild.sh, line 136: Called src_compile
* environment, line 5178: Called virtx './mach' 'build' '--verbose'
* environment, line 6685: Called die
* The specific snippet of code:
* [[ ${retval} -ne 0 ]] && die "Failed to run '$@'";
*
* If you need support, post the output of `emerge --info '=www-client/firefox-128.4.0::gentoo'`,
* the complete build log and the output of `emerge -pqv '=www-client/firefox-128.4.0::gentoo'`.
* The complete build log is located at '/var/tmp/portage/www-client/firefox-128.4.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/www-client/firefox-128.4.0/temp/environment'.
* Working directory: '/var/tmp/portage/www-client/firefox-128.4.0/work/firefox-128.4.0'
* S: '/var/tmp/portage/www-client/firefox-128.4.0/work/firefox-128.4.0'

Further firefox was compiled without problems, after update to 128 version the problem is occurred. MAKEOPTS is on "-j1" setup.

I googled the Internet, but unfortunately I did not find the reason, maybe someone has already encountered this.

Thanks a lot for ideas,

[Juippisi]

Nothing can be said from that error. You should open a bug in bugs.gentoo.org. Post your emerge --info and full build.log file. If the log file is too big, you can "xz -9" to compress it and post as compressed archive.

[steveo314]

Will it compile if you add

Code: Select all

-lto -pgo

to your

Code: Select all

USE

[ruby_R53]

maybe you just don't have enough resources (like RAM maybe) to compile it? i had a similar error when compiling Chromium, fixed it by making a huge swap file

[sam_]

I would recommend speculation be avoided until logs are provided.

[alogim]

Also got the same error a few minutes ago, with -j 32 in my MAKEOPTS.
Lowering the amounts of parallel jobs did the trick for me.
I would suggest to maybe monitor your RAM usage, just to make sure it is not a memory problem.

[Juippisi]

We recently flipped the default clang use flag off. By default it now builds the browser with gcc, which requires more memory. If you had no problems building Firefox before, I'd suggest enabling the clang use flag back for it.

Most likely the +clang use flag will be enabled again soon, since we now have slotted rust available in Gentoo that solves the common problems we had with +clang previously.

[rogge]

I'd the very same issue recently. The fix was indeed '-clang'.

Thanks!