Gentoo Forums :: View topic - Firefox-91.10.0 Compile problem

Firefox-91.10.0 Compile problem

View unanswered posts
View posts from last 24 hours

Goto page 1, 2 Next

Gentoo Forums Forum Index

Portage & Programming

View previous topic :: View next topic

Author

Message

sleepingsun
Guru
Guru

Joined: 03 May 2006
Posts: 458
Location: Bosnia

Posted: Wed Jun 29, 2022 12:53 pm Post subject: Firefox-91.10.0 Compile problem

Hi friends

I need help i can compile firefox and need help to solve problem

Code:

65:15.54 Finished release [optimized] target(s) in 63m 37s
65:15.65 warning: the following packages contain code that will be rejected by a future version of Rust: cascade_bloom_filter v0.1.0 (/var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0/toolkit/components/cascade_bloom_filter), cert_storage v0.0.1 (/var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0/security/manager/ssl/cert_storage), rental v0.5.6
65:15.73 note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 1`
65:16.80 gmake[4]: Leaving directory '/var/tmp/portage/www-client/firefox-91.10.0/work/firefox_build/toolkit/library/rust'
65:16.81 gmake[3]: Leaving directory '/var/tmp/portage/www-client/firefox-91.10.0/work/firefox_build'
65:16.81 gmake[2]: *** [/var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0/config/recurse.mk:34: compile] Error 2
65:16.81 gmake[2]: Leaving directory '/var/tmp/portage/www-client/firefox-91.10.0/work/firefox_build'
65:16.81 gmake[1]: *** [/var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0/config/rules.mk:355: default] Error 2
65:16.87 gmake[1]: Leaving directory '/var/tmp/portage/www-client/firefox-91.10.0/work/firefox_build'
65:16.87 gmake: *** [client.mk:65: build] Error 2
65:16.88 31 compiler warnings present.
* ERROR: www-client/firefox-91.10.0::gentoo failed (compile phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 127: Called src_compile
* environment, line 5160: Called die
* The specific snippet of code:
* ${virtx_cmd} ./mach build --verbose || die
*
* If you need support, post the output of `emerge --info '=www-client/firefox-91.10.0::gentoo'`,
* the complete build log and the output of `emerge -pqv '=www-client/firefox-91.10.0::gentoo'`.
* The complete build log is located at '/var/tmp/portage/www-client/firefox-91.10.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/www-client/firefox-91.10.0/temp/environment'.
* Working directory: '/var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0'
* S: '/var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0'

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

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

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

* <media-libs/dav1d-1.0.0 detected, removing 1.0.0 compat patch.
* ERROR: www-client/firefox-91.10.0::gentoo failed (compile phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 127: Called src_compile
* environment, line 5160: Called die
* The specific snippet of code:
* ${virtx_cmd} ./mach build --verbose || die
*
* If you need support, post the output of `emerge --info '=www-client/firefox-91.10.0::gentoo'`,
* the complete build log and the output of `emerge -pqv '=www-client/firefox-91.10.0::gentoo'`.
* The complete build log is located at '/var/tmp/portage/www-client/firefox-91.10.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/www-client/firefox-91.10.0/temp/environment'.
* Working directory: '/var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0'
* S: '/var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0'

_________________
Gentoo is Rocks

eccerr0r
Watchman

Joined: 01 Jul 2004
Posts: 9709
Location: almost Mile High in the USA

Posted: Wed Jun 29, 2022 4:01 pm Post subject:

Without the build log, hard to tell what the problem is... However probably same as this other thread -- please check to see if it's the same problem with its workarounds. _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD What am I supposed watching?

colo-des
Tux's lil' helper

Joined: 20 May 2011
Posts: 97

Posted: Wed Jun 29, 2022 6:53 pm Post subject:

Exactly the same error happened to me with firefox-91.8.0
It was resolved by enabling the use system-llvm of the rust package, since by default it comes with an internal version 13.0.0

Code:

$ rustc --version --verbose
rustc 1.59.0
binary: rustc
commit-hash: unknown
commit-date: unknown
host: x86_64-unknown-linux-gnu
release: 1.59.0
LLVM version: 13.0.0

After emerging rust by enabling use system-llvm.

Code:

$ rustc --version --verbose
rustc 1.59.0
binary: rustc
commit-hash: unknown
commit-date: unknown
host: x86_64-unknown-linux-gnu
release: 1.59.0
LLVM version: 13.0.1

I have disliked the massive inclusion of all architectures in LLVM, leaving only X86 and AMDGPU
to shorten the madness of compiling for architectures that I don't have and never will have.

Code:

$ cat /etc/portage/make.conf |grep LLVM_TARGETS
LLVM_TARGETS="X86 AMDGPU"

Code:

$ cat /etc/portage/profile/package.use.force/llvm
*/* -llvm_targets_AArch64
*/* -llvm_targets_ARC
*/* -llvm_targets_ARM
*/* -llvm_targets_AVR
*/* -llvm_targets_CSKY
*/* -llvm_targets_Hexagon
*/* -llvm_targets_Lanai
*/* -llvm_targets_LoongArch
*/* -llvm_targets_M68k
*/* -llvm_targets_MSP430
*/* -llvm_targets_Mips
*/* -llvm_targets_NVPTX
*/* -llvm_targets_PowerPC
*/* -llvm_targets_RISCV
*/* -llvm_targets_Sparc
*/* -llvm_targets_SystemZ
*/* -llvm_targets_VE
*/* -llvm_targets_WebAssembly
*/* -llvm_targets_XCore
*/* -llvm_targets_BPF

I then compiled llvm rust clang in that order.

Code:

$ llc -version
LLVM (http://llvm.org/):
LLVM version 13.0.1
Optimized build.
Default target: x86_64-pc-linux-gnu
Host CPU: bdver2

Registered Targets:
amdgcn - AMD GCN GPUs
r600 - AMD GPUs HD2XXX-HD6XXX
x86 - 32-bit X86: Pentium-Pro and above
x86-64 - 64-bit X86: EM64T and AMD64

Code:

$ clang --version
clang version 13.0.1
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/lib/llvm/13/bin

Good luck with that and I hope you can figure it out.

sleepingsun
Guru
Guru

Joined: 03 May 2006
Posts: 458
Location: Bosnia

Posted: Fri Jul 01, 2022 9:31 am Post subject:

Code:

rustc --version --verbose
rustc 1.60.0 (gentoo)
binary: rustc
commit-hash: unknown
commit-date: unknown
host: x86_64-unknown-linux-gnu
release: 1.60.0
LLVM version: 14.0.0

Code:

cat /etc/portage/make.conf |grep LLVM_TARGETS

nothing here

Code:

cat /etc/portage/profile/package.use.force/llvm
cat: /etc/portage/profile/package.use.force/llvm: No such file or directory

Code:

clang version 14.0.4
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/lib/llvm/14/bin

Code:

llc -version
LLVM (http://llvm.org/):
LLVM version 14.0.4
Optimized build.
Default target: x86_64-pc-linux-gnu
Host CPU: core2

Registered Targets:
aarch64 - AArch64 (little endian)
aarch64_32 - AArch64 (little endian ILP32)
aarch64_be - AArch64 (big endian)
amdgcn - AMD GCN GPUs
arm - ARM
arm64 - ARM64 (little endian)
arm64_32 - ARM64 (little endian ILP32)
armeb - ARM (big endian)
avr - Atmel AVR Microcontroller
bpf - BPF (host endian)
bpfeb - BPF (big endian)
bpfel - BPF (little endian)
hexagon - Hexagon
lanai - Lanai
mips - MIPS (32-bit big endian)
mips64 - MIPS (64-bit big endian)
mips64el - MIPS (64-bit little endian)
mipsel - MIPS (32-bit little endian)
msp430 - MSP430 [experimental]
nvptx - NVIDIA PTX 32-bit
nvptx64 - NVIDIA PTX 64-bit
ppc32 - PowerPC 32
ppc32le - PowerPC 32 LE
ppc64 - PowerPC 64
ppc64le - PowerPC 64 LE
r600 - AMD GPUs HD2XXX-HD6XXX
riscv32 - 32-bit RISC-V
riscv64 - 64-bit RISC-V
sparc - Sparc
sparcel - Sparc LE
sparcv9 - Sparc V9
systemz - SystemZ
thumb - Thumb
thumbeb - Thumb (big endian)
ve - VE
wasm32 - WebAssembly 32-bit
wasm64 - WebAssembly 64-bit
x86 - 32-bit X86: Pentium-Pro and above
x86-64 - 64-bit X86: EM64T and AMD64
xcore - XCore

_________________
Gentoo is Rocks

colo-des
Tux's lil' helper

Joined: 20 May 2011
Posts: 97

Posted: Fri Jul 01, 2022 7:06 pm Post subject:

You must activate the use system-llvm of the rust package, that is done in the file /etc/portage/package.use or in /etc/portage/package.use/package.use
If the file is not there, create it and put this line inside:

Code:

dev-lang/rust system-llvm

In my case I usually put all the uses of the package, both enabled and disabled to improve the documentation in future revisions, so I have:

Code:

dev-lang/rust system-llvm -system-bootstrap -clippy -debug -libressl -miri -nightly -parallel-compiler -rls -rustfmt -test -wasm abi_x86_32

Regarding llvm, they have recently decided (I think due to an unresolved bug of some strange architecture) to ignore what the user indicated in
its /etc/portage/make.conf on which architectures llvm should support, that is defined using LLVM_TARGETS inside /etc/portage/make.conf
in my case as i have AMD video i use LLVM_TARGETS="X86 AMDGPU" other options will be if you use another video chip like intel or nvidia.
To reverse and make it pay attention to what is indicated by LLVM_TARGETS in /etc/portage/make.conf, a file called /etc/portage/profile/package.use.force/llvm must be created.
and inside put the architectures that you do not want to compile, when compiling llvm rust and clang, that is, all the rest that you do not select in LLVM_TARGETS
inside /etc/portage/make.conf

Create the package.use folder if it doesn't exist:

Code:

# mkdir -p /etc/portage/profile/package.use.force

Create the llvm file inside the package.use folder with that content or the one of your choice for architectures you don't want to have supported

Code:

# nano /etc/portage/profile/package.use.force/llvm
*/* -llvm_targets_AArch64
*/* -llvm_targets_ARC
*/* -llvm_targets_ARM
*/* -llvm_targets_AVR
*/* -llvm_targets_CSKY
*/* -llvm_targets_Hexagon
*/* -llvm_targets_Lanai
*/* -llvm_targets_LoongArch
*/* -llvm_targets_M68k
*/* -llvm_targets_MSP430
*/* -llvm_targets_Mips
*/* -llvm_targets_NVPTX
*/* -llvm_targets_PowerPC
*/* -llvm_targets_RISCV
*/* -llvm_targets_Sparc
*/* -llvm_targets_SystemZ
*/* -llvm_targets_VE
*/* -llvm_targets_WebAssembly
*/* -llvm_targets_XCore
*/* -llvm_targets_BPF

The advantage of leaving only the architectures you use is that the compilation time of the packages will be much less and less susceptible to compilation bugs.
in other architectures that you do not have and will not have.

Now you emerge llvm rust and clang.

Code:

# emerge -av1 llvm rust clang

Emerge will show you in red the use system-llvm and the active architectures to compile, make sure they are correct for your hardware.
In my case I have llvm-13.0.1 and rust-1.59 because I haven't updated in a while, but seeing that the error is the same
that it gave me, I suppose it is because the internal llvm version that rust brings is older, in your case you have
the internal llvm version 14.0.0 but then on the outside you have the llvm-14.0.4 package, once you have finished following the steps that I gave you
You should have this rust output:

Code:

$ rustc --version --verbose
rustc 1.60.0 (gentoo)
binary: rustc
commit-hash: unknown
commit-date: unknown
host: x86_64-unknown-linux-gnu
release: 1.60.0
LLVM version: 14.0.4

I hope I haven't confused you more than I tried to help you.
Cheers

sleepingsun
Guru
Guru

Joined: 03 May 2006
Posts: 458
Location: Bosnia

Posted: Sat Jul 02, 2022 8:52 am Post subject:

I done as you told me all things and compile will post when finished

Code:

Just this one is read only and directory
/etc/portage/package.use

Code:

i created there package.use and put
dev-lang/rust system-llvm

But when i startted :

Code:

emerge -av1 llvm rust clang

i get changed only this created by forced part in rust still see in (-system-llvm)

and put in make.conf also system-llvm

But i start upgrade anyway
_________________
Gentoo is Rocks

Hu
Administrator

Joined: 06 Mar 2007
Posts: 21842

Posted: Sat Jul 02, 2022 3:37 pm Post subject:

Please post the output of emerge --pretend --verbose dev-lang/rust so we can try to understand why that flag is USE-masked for you.

sleepingsun
Guru
Guru

Joined: 03 May 2006
Posts: 458
Location: Bosnia

Posted: Sat Jul 02, 2022 7:55 pm Post subject:

Code:

emerge --pretend --verbose dev-lang/rust

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild R ] dev-lang/rust-1.60.0:stable/1.60::gentoo USE="-clippy -debug -dist -doc (-miri) (-nightly) (-parallel-compiler) (-profiler) -rls -rust-src -rustfmt (-system-bootstrap) (-system-llvm) -test -verify-sig -wasm" ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="sse2" LLVM_TARGETS="(X86) -AArch64 -AMDGPU -ARM -AVR -BPF -Hexagon -Lanai -MSP430 -Mips -NVPTX -PowerPC -RISCV -Sparc -SystemZ -WebAssembly -XCore" 0 KiB

Total: 1 package (1 reinstall), Size of downloads: 0 KiB

After colo-des post i do i have another error :

Code:

0:12.25 Refreshing /var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0/old-configure with /var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0/build/autoconf/autoconf.sh
0:12.49 creating cache ./config.cache
0:12.53 checking host system type... x86_64-pc-linux-gnu
0:12.55 checking target system type... x86_64-pc-linux-gnu
0:12.57 checking build system type... x86_64-pc-linux-gnu
0:12.57 checking for objcopy... /usr/bin/objcopy
0:12.62 checking for Cygwin environment... no
0:12.67 checking for mingw32 environment... no
0:12.76 checking for executable suffix... configure: error: installation or configuration problem: compiler cannot create executables.
0:12.76 DEBUG: <truncated - see config.log for full output>
0:12.76 DEBUG: ; return 0; }
0:12.76 DEBUG: configure:872: checking for mingw32 environment
0:12.76 DEBUG: configure:884: /usr/lib/llvm/14/bin/x86_64-pc-linux-gnu-clang -std=gnu99 -c -march=native -pipe conftest.c 1>&5
0:12.76 DEBUG: configure:880:8: error: use of undeclared identifier '__MINGW32__'
0:12.76 DEBUG: return __MINGW32__;
0:12.76 DEBUG: ^
0:12.76 DEBUG: 1 error generated.
0:12.76 DEBUG: configure: failed program was:
0:12.76 DEBUG: #line 877 "configure"
0:12.76 DEBUG: #include "confdefs.h"
0:12.76 DEBUG:
0:12.76 DEBUG: int main() {
0:12.76 DEBUG: return __MINGW32__;
0:12.76 DEBUG: ; return 0; }
0:12.76 DEBUG: configure:903: checking for executable suffix
0:12.76 DEBUG: configure:913: /usr/lib/llvm/14/bin/x86_64-pc-linux-gnu-clang -std=gnu99 -o conftest -march=native -pipe -Wl,-O1 -Wl,--as-needed -Wl,--compress-debug-sections=zlib -Wl,-rpath=/usr/lib64/firefox,--enable-new-dtags -fuse-ld=lld conftest.c 1>&5
0:12.76 DEBUG: /usr/bin/ld.lld: symbol lookup error: /usr/bin/../lib64/liblldELF.so.14: undefined symbol: LLVMInitializeVETargetInfo, version LLVM_14
0:12.76 DEBUG: clang-14: error: unable to execute command: No such file or directory
0:12.76 DEBUG: clang-14: error: linker command failed due to signal (use -v to see invocation)
0:12.76 DEBUG: configure: error: installation or configuration problem: compiler cannot create executables.
0:12.76 ERROR: old-configure failed
Error running mach:

['configure']

The error occurred in code that was called by the mach command. This is either
a bug in the called code itself or in the way that mach is calling it.
You can invoke |./mach busted| to check if this issue is already on file. If it
isn't, please use |./mach busted file configure| to report it. If |./mach busted| is
misbehaving, you can also inspect the dependencies of bug 1543241.

If filing a bug, please include the full output of mach, including this error
message.

The details of the failure are as follows:

Exception: Process executed with non-0 exit code 1: ['/usr/bin/python3.10', '/var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0/configure.py']

File "/var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0/python/mozbuild/mozbuild/build_commands.py", line 185, in configure
return driver.configure(
File "/var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0/python/mozbuild/mozbuild/controller/building.py", line 1528, in configure
status = self._run_command_in_objdir(
File "/var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0/python/mozbuild/mozbuild/base.py", line 845, in _run_command_in_objdir
return self.run_process(cwd=self.topobjdir, **args)
File "/var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0/python/mach/mach/mixin/process.py", line 176, in run_process
raise Exception(
* ERROR: www-client/firefox-91.10.0::gentoo failed (configure phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 127: Called src_configure
* environment, line 5390: Called die
* The specific snippet of code:
* ./mach configure || die
*
* If you need support, post the output of `emerge --info '=www-client/firefox-91.10.0::gentoo'`,
* the complete build log and the output of `emerge -pqv '=www-client/firefox-91.10.0::gentoo'`.
* The complete build log is located at '/var/tmp/portage/www-client/firefox-91.10.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/www-client/firefox-91.10.0/temp/environment'.
* Working directory: '/var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0'
* S: '/var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0'

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

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

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

* <media-libs/dav1d-1.0.0 detected, removing 1.0.0 compat patch.
* ERROR: www-client/firefox-91.10.0::gentoo failed (configure phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 127: Called src_configure
* environment, line 5390: Called die
* The specific snippet of code:
* ./mach configure || die
*
* If you need support, post the output of `emerge --info '=www-client/firefox-91.10.0::gentoo'`,
* the complete build log and the output of `emerge -pqv '=www-client/firefox-91.10.0::gentoo'`.
* The complete build log is located at '/var/tmp/portage/www-client/firefox-91.10.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/www-client/firefox-91.10.0/temp/environment'.
* Working directory: '/var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0'
* S: '/var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0'

my graphic card is :

Code:

VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 710] (rev a1)

_________________
Gentoo is Rocks

Last edited by sleepingsun on Sat Jul 02, 2022 8:03 pm; edited 1 time in total

sam_
Developer

Joined: 14 Aug 2020
Posts: 1707

Posted: Sat Jul 02, 2022 7:57 pm Post subject:

That error is exactly why all LLVM targets are forced on. Try emerge -v1 lld.

sleepingsun
Guru
Guru

Joined: 03 May 2006
Posts: 458
Location: Bosnia

Posted: Sat Jul 02, 2022 9:59 pm Post subject:

And back to first error ...

Code:

77:49.01 Finished release [optimized] target(s) in 75m 46s
77:49.04 warning: the following packages contain code that will be rejected by a future version of Rust: cascade_bloom_filter v0.1.0 (/var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0/toolkit/components/cascade_bloom_filter), cert_storage v0.0.1 (/var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0/security/manager/ssl/cert_storage), rental v0.5.6
77:49.11 note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 1`
77:49.75 gmake[4]: Leaving directory '/var/tmp/portage/www-client/firefox-91.10.0/work/firefox_build/toolkit/library/rust'
77:49.75 gmake[3]: Leaving directory '/var/tmp/portage/www-client/firefox-91.10.0/work/firefox_build'
77:49.75 gmake[2]: *** [/var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0/config/recurse.mk:34: compile] Error 2
77:49.75 gmake[2]: Leaving directory '/var/tmp/portage/www-client/firefox-91.10.0/work/firefox_build'
77:49.75 gmake[1]: *** [/var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0/config/rules.mk:355: default] Error 2
77:49.75 gmake[1]: Leaving directory '/var/tmp/portage/www-client/firefox-91.10.0/work/firefox_build'
77:49.75 gmake: *** [client.mk:65: build] Error 2
77:49.75 31 compiler warnings present.
* ERROR: www-client/firefox-91.10.0::gentoo failed (compile phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 127: Called src_compile
* environment, line 5164: Called die
* The specific snippet of code:
* ${virtx_cmd} ./mach build --verbose || die
*
* If you need support, post the output of `emerge --info '=www-client/firefox-91.10.0::gentoo'`,
* the complete build log and the output of `emerge -pqv '=www-client/firefox-91.10.0::gentoo'`.
* The complete build log is located at '/var/tmp/portage/www-client/firefox-91.10.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/www-client/firefox-91.10.0/temp/environment'.
* Working directory: '/var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0'
* S: '/var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0'

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

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

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

* <media-libs/dav1d-1.0.0 detected, removing 1.0.0 compat patch.
* ERROR: www-client/firefox-91.10.0::gentoo failed (compile phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 127: Called src_compile
* environment, line 5164: Called die
* The specific snippet of code:
* ${virtx_cmd} ./mach build --verbose || die
*
* If you need support, post the output of `emerge --info '=www-client/firefox-91.10.0::gentoo'`,
* the complete build log and the output of `emerge -pqv '=www-client/firefox-91.10.0::gentoo'`.
* The complete build log is located at '/var/tmp/portage/www-client/firefox-91.10.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/www-client/firefox-91.10.0/temp/environment'.
* Working directory: '/var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0'
* S: '/var/tmp/portage/www-client/firefox-91.10.0/work/firefox-91.10.0'

_________________
Gentoo is Rocks

colo-des
Tux's lil' helper

Joined: 20 May 2011
Posts: 97

Posted: Sun Jul 03, 2022 1:17 am Post subject:

Looking at the rust-1.60.0 ebuild I see that it has use system-llvm:
https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-lang/rust/rust-1.60.0.ebuild

But when it emerges it appears disabled (-system-llvm) I understand the parenthesis means that they removed the use or forced it to be disabled?
I don't see any profile file that is forcing the use to disable -system-llvm
However, you could try to force it to be activated by creating the file /etc/portage/profile/package.use.force/rust with this content:

Code:

# mkdir -p /etc/portage/profile/package.use.force
# nano /etc/portage/profile/package.use.force/rust
dev-lang/rust system-llvm

If when trying to emerge rust, that use appears disabled (-system-llvm) or -system-llvm does not make sense to emerge rust, the use system-llvm should appear
in red indicating that rust will use the installed llvm package and not the internal version that comes with rust.

Code:

$ equery uses rust
..
..
+ + system-llvm : Use the system LLVM install
..
..

Then if you have nvidia video, the use you should enable for LLVM_TARGETS in /etc/portage/make.conf would be LLVM_TARGETS="X86 NVPTX" although I don't know
What video driver do you use for your nvidia video card, I don't know what to use for nvidia.

Honestly, rust is an experiment for me...it can't be that the language changes and updates at the speed it does.
...if that's serious language, then I'm an astronaut.

Cheers

Josef.95
Advocate

Joined: 03 Sep 2007
Posts: 4601
Location: Germany

Posted: Sun Jul 03, 2022 6:15 am Post subject:

sleepingsun wrote:

And back to first error ...

Code:

Hi,

I think this "Error 2" sniped is probably not the first error in build.log.
Can you please share the full build.log (best make it with MAKEOPTS="-j1" after a fresh "emerge --sync" from current stable firefox-91.11.0:esr version) and the "emerge --info"?

sleepingsun
Guru
Guru

Joined: 03 May 2006
Posts: 458
Location: Bosnia

Posted: Sun Jul 03, 2022 8:34 am Post subject:

colo_des i do as you told me i get this :

Code:

equery uses rust
[ Legend : U - final flag setting for installation]
[ : I - package is installed with flag ]
[ Colors : set, unset ]
* Found these USE flags for dev-lang/rust-1.60.0:
U I
- - abi_x86_32 : 32-bit (x86) libraries
- - clippy : Install clippy, Rust code linter
+ + cpu_flags_x86_sse2 : Use the SSE2 instruction set
- - debug : Enable extra debug codepaths, like asserts and extra output. If you
want to get meaningful backtraces see
https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces
- - dist : Install dist tarballs (used for bootstrapping)
- - doc : Add extra documentation (API, Javadoc, etc). It is recommended to
enable per package instead of globally
- - llvm_targets_AArch64 : AArch64 CPU target (arm64 in Gentoo)
- - llvm_targets_AMDGPU : AMDGPU target (supports R600 and GCN GPUs)
- - llvm_targets_ARM : ARM CPU target
- - llvm_targets_AVR : 8-bit Atmel AVR microcontroller target
- - llvm_targets_BPF : Berkeley Packet Filter target
- - llvm_targets_Hexagon : Qualcomm Hexagon DSP target
- - llvm_targets_Lanai : Lanai CPU target
- - llvm_targets_MSP430 : MSP430 CPU target (experimental)
- - llvm_targets_Mips : MIPS CPU target (includes MIPS64)
- - llvm_targets_NVPTX : NVIDIA PTX (GPU) target (32-bit and 64-bit)
- - llvm_targets_PowerPC : PowerPC CPU target (PPC32 and PPC64)
- - llvm_targets_RISCV : RISC-V CPU target
- - llvm_targets_Sparc : Sparc CPU target
- - llvm_targets_SystemZ : SystemZ (s390x) CPU target
- - llvm_targets_WebAssembly : WebAssembly backend
- - llvm_targets_XCore : XCore CPU target
- - rls : Install rls, Rust Language Server (used with IDEs supporting RLS
protocol)
- - rust-src : Install rust-src, needed by developer tools and for build-std
(cross)
- - rustfmt : Install rustfmt, Rust code formatter
- - test : Enable dependencies and/or preparations necessary to run tests
(usually controlled by FEATURES=test but can be toggled
independently)
- - verify-sig : Verify upstream signatures on distfiles
- - wasm : Build support for the wasm32-unknown-unknown target

Code:

_________________
Gentoo is Rocks

Ionen
Developer

Joined: 06 Dec 2018
Posts: 2732

Posted: Sun Jul 03, 2022 8:53 am Post subject:

As Josef.95 pointed, the actual error is not shown. So there's no way to tell what happened without seeing more of the log (ideally the full log so don't keep going back & forth about what's missing). But to guess, as pointed by this earlier post I also suspect it's the crc32 thing (bug #838373) given it usually makes it to "Finished", would have something like error: always_inline function '_mm_crc32_u8' in the log near Error 1

sleepingsun
Guru
Guru

Joined: 03 May 2006
Posts: 458
Location: Bosnia

Posted: Sun Jul 03, 2022 11:03 am Post subject:

Ionen wrote:

As Josef.95 pointed, the actual error is not shown. So there's no way to tell what happened without seeing more of the log (ideally the full log so don't keep going back & forth about what's missing).

But to guess, as pointed by this earlier post I also suspect it's the crc32 thing (bug #838373) given it usually makes it to "Finished", would have something like error: always_inline function '_mm_crc32_u8' in the log near Error 1

Yes i try also J1 and all can do but i have enough ram always back for this error i just update to new 91.11 firefox and we will see what happen

Its look like much easy install whole Gentoo system with services than this Firefox !

new firefox give me this error:

Code:

/libpng16 -pthread -fexperimental-new-pass-manager -MD -MP -MF .deps/SkOpts_sse42.o.pp -fcolor-diagnostics -O3 -msse4.2 /var/tmp/portage/www-client/firefox-91.11.0/work/firefox-91.11.0/gfx/skia/skia/src/opts/SkOpts_sse42.cpp
213:15.09 In file included from /var/tmp/portage/www-client/firefox-91.11.0/work/firefox-91.11.0/gfx/skia/skia/src/opts/SkOpts_sse42.cpp:11:
213:15.09 /var/tmp/portage/www-client/firefox-91.11.0/work/firefox-91.11.0/gfx/skia/skia/src/opts/SkChecksum_opts.h:39:21: error: always_inline function '_mm_crc32_u64' requires target feature 'crc32', but would be inlined into function 'hash_fn' that is compiled without support for 'crc32'
213:15.09 a = _mm_crc32_u64(a, sk_unaligned_load<uint64_t>(data+ 0));
213:15.09 ^
213:15.09 /var/tmp/portage/www-client/firefox-91.11.0/work/firefox-91.11.0/gfx/skia/skia/src/opts/SkChecksum_opts.h:40:21: error: always_inline function '_mm_crc32_u64' requires target feature 'crc32', but would be inlined into function 'hash_fn' that is compiled without support for 'crc32'
213:15.09 b = _mm_crc32_u64(b, sk_unaligned_load<uint64_t>(data+ 8));
213:15.09 ^
213:15.09 /var/tmp/portage/www-client/firefox-91.11.0/work/firefox-91.11.0/gfx/skia/skia/src/opts/SkChecksum_opts.h:41:21: error: always_inline function '_mm_crc32_u64' requires target feature 'crc32', but would be inlined into function 'hash_fn' that is compiled without support for 'crc32'
213:15.09 c = _mm_crc32_u64(c, sk_unaligned_load<uint64_t>(data+16));
213:15.10 ^
213:15.10 /var/tmp/portage/www-client/firefox-91.11.0/work/firefox-91.11.0/gfx/skia/skia/src/opts/SkChecksum_opts.h:45:37: error: always_inline function '_mm_crc32_u32' requires target feature 'crc32', but would be inlined into function 'hash_fn' that is compiled without support for 'crc32'
213:15.10 hash = _mm_crc32_u32(a, _mm_crc32_u32(b, c));
213:15.10 ^
213:15.10 /var/tmp/portage/www-client/firefox-91.11.0/work/firefox-91.11.0/gfx/skia/skia/src/opts/SkChecksum_opts.h:45:20: error: always_inline function '_mm_crc32_u32' requires target feature 'crc32', but would be inlined into function 'hash_fn' that is compiled without support for 'crc32'
213:15.10 hash = _mm_crc32_u32(a, _mm_crc32_u32(b, c));
213:15.10 ^
213:15.11 /var/tmp/portage/www-client/firefox-91.11.0/work/firefox-91.11.0/gfx/skia/skia/src/opts/SkChecksum_opts.h:50:20: error: always_inline function '_mm_crc32_u64' requires target feature 'crc32', but would be inlined into function 'hash_fn' that is compiled without support for 'crc32'
213:15.11 hash = _mm_crc32_u64(hash, sk_unaligned_load<uint64_t>(data));
213:15.11 ^
213:15.11 /var/tmp/portage/www-client/firefox-91.11.0/work/firefox-91.11.0/gfx/skia/skia/src/opts/SkChecksum_opts.h:57:20: error: always_inline function '_mm_crc32_u64' requires target feature 'crc32', but would be inlined into function 'hash_fn' that is compiled without support for 'crc32'
213:15.11 hash = _mm_crc32_u64(hash, sk_unaligned_load<uint64_t>(data));
213:15.11 ^
213:15.11 /var/tmp/portage/www-client/firefox-91.11.0/work/firefox-91.11.0/gfx/skia/skia/src/opts/SkChecksum_opts.h:66:22: error: always_inline function '_mm_crc32_u32' requires target feature 'crc32', but would be inlined into function 'hash_fn' that is compiled without support for 'crc32'
213:15.11 hash32 = _mm_crc32_u32(hash32, sk_unaligned_load<uint32_t>(data));
213:15.11 ^
213:15.11 /var/tmp/portage/www-client/firefox-91.11.0/work/firefox-91.11.0/gfx/skia/skia/src/opts/SkChecksum_opts.h:70:22: error: always_inline function '_mm_crc32_u16' requires target feature 'crc32', but would be inlined into function 'hash_fn' that is compiled without support for 'crc32'
213:15.11 hash32 = _mm_crc32_u16(hash32, sk_unaligned_load<uint16_t>(data));
213:15.11 ^
213:15.11 /var/tmp/portage/www-client/firefox-91.11.0/work/firefox-91.11.0/gfx/skia/skia/src/opts/SkChecksum_opts.h:74:22: error: always_inline function '_mm_crc32_u8' requires target feature 'crc32', but would be inlined into function 'hash_fn' that is compiled without support for 'crc32'
213:15.11 hash32 = _mm_crc32_u8(hash32, sk_unaligned_load<uint8_t>(data));
213:15.11 ^
213:15.11 10 errors generated.
213:15.11 gmake[4]: *** [/var/tmp/portage/www-client/firefox-91.11.0/work/firefox-91.11.0/config/rules.mk:676: SkOpts_sse42.o] Error 1
213:15.11 gmake[4]: Leaving directory '/var/tmp/portage/www-client/firefox-91.11.0/work/firefox_build/gfx/skia'
213:15.11 gmake[3]: *** [/var/tmp/portage/www-client/firefox-91.11.0/work/firefox-91.11.0/config/recurse.mk:72: gfx/skia/target-objects] Error 2
213:15.11 gmake[3]: Leaving directory '/var/tmp/portage/www-client/firefox-91.11.0/work/firefox_build'
213:15.11 gmake[2]: *** [/var/tmp/portage/www-client/firefox-91.11.0/work/firefox-91.11.0/config/recurse.mk:34: compile] Error 2
213:15.11 gmake[2]: Leaving directory '/var/tmp/portage/www-client/firefox-91.11.0/work/firefox_build'
213:15.11 gmake[1]: *** [/var/tmp/portage/www-client/firefox-91.11.0/work/firefox-91.11.0/config/rules.mk:355: default] Error 2
213:15.11 gmake[1]: Leaving directory '/var/tmp/portage/www-client/firefox-91.11.0/work/firefox_build'
213:15.11 gmake: *** [client.mk:65: build] Error 2
213:15.11 31 compiler warnings present.
* ERROR: www-client/firefox-91.11.0::gentoo failed (compile phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 127: Called src_compile
* environment, line 5164: Called die
* The specific snippet of code:
* ${virtx_cmd} ./mach build --verbose || die
*
* If you need support, post the output of `emerge --info '=www-client/firefox-91.11.0::gentoo'`,
* the complete build log and the output of `emerge -pqv '=www-client/firefox-91.11.0::gentoo'`.
* The complete build log is located at '/var/tmp/portage/www-client/firefox-91.11.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/www-client/firefox-91.11.0/temp/environment'.
* Working directory: '/var/tmp/portage/www-client/firefox-91.11.0/work/firefox-91.11.0'
* S: '/var/tmp/portage/www-client/firefox-91.11.0/work/firefox-91.11.0'

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

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

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

* <media-libs/dav1d-1.0.0 detected, removing 1.0.0 compat patch.
* ERROR: www-client/firefox-91.11.0::gentoo failed (compile phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 127: Called src_compile
* environment, line 5164: Called die
* The specific snippet of code:
* ${virtx_cmd} ./mach build --verbose || die
*
* If you need support, post the output of `emerge --info '=www-client/firefox-91.11.0::gentoo'`,
* the complete build log and the output of `emerge -pqv '=www-client/firefox-91.11.0::gentoo'`.
* The complete build log is located at '/var/tmp/portage/www-client/firefox-91.11.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/www-client/firefox-91.11.0/temp/environment'.
* Working directory: '/var/tmp/portage/www-client/firefox-91.11.0/work/firefox-91.11.0'
* S: '/var/tmp/portage/www-client/firefox-91.11.0/work/firefox-91.11.0'

as build log 10mb can upload it with wgetpaste and I upload to mediashare

Code:

https://www.mediafire.com/file/fb6vxzu79a9elwv/build.log/file

_________________
Gentoo is Rocks

Josef.95
Advocate

Joined: 03 Sep 2007
Posts: 4601
Location: Germany

Posted: Sun Jul 03, 2022 4:04 pm Post subject:

Yes, go back to first post from @eccerr0r -> https://forums.gentoo.org/viewtopic-p-8722565.html#8722565 ;) I would try the workaround without -march=native

colo-des
Tux's lil' helper

Joined: 20 May 2011
Posts: 97

Posted: Sun Jul 03, 2022 6:15 pm Post subject:

Well, I see that they have effectively removed the use system-llvm, which for me was the only solution to be able to emerge firefox.
I will not update anymore and here will be the versions that I have installed in my local tree... I have already started to read something
of LFS, to the good understanding... few words.

Code:

$ equery uses rust
[ Legend : U - final flag setting for installation]
[ : I - package is installed with flag ]
[ Colors : set, unset ]
* Found these USE flags for dev-lang/rust-1.59.0:
U I
+ + abi_x86_32 : 32-bit (x86) libraries
- - clippy : Install clippy, Rust code linter
+ + cpu_flags_x86_sse2 : Use the SSE2 instruction set
- - debug : Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see
https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces
- - dist : Install dist tarballs (used for bootstrapping)
- - doc : Add extra documentation (API, Javadoc, etc). It is recommended to enable per package instead of globally
- - llvm_targets_AArch64 : AArch64 CPU target (arm64 in Gentoo)
+ + llvm_targets_AMDGPU : AMDGPU target (supports R600 and GCN GPUs)
- - llvm_targets_ARM : ARM CPU target
- - llvm_targets_AVR : 8-bit Atmel AVR microcontroller target
- - llvm_targets_BPF : Berkeley Packet Filter target
- - llvm_targets_Hexagon : Qualcomm Hexagon DSP target
- - llvm_targets_Lanai : Lanai CPU target
- - llvm_targets_MSP430 : MSP430 CPU target (experimental)
- - llvm_targets_Mips : MIPS CPU target (includes MIPS64)
- - llvm_targets_NVPTX : NVIDIA PTX (GPU) target (32-bit and 64-bit)
- - llvm_targets_PowerPC : PowerPC CPU target (PPC32 and PPC64)
- - llvm_targets_RISCV : RISC-V CPU target
- - llvm_targets_Sparc : Sparc CPU target
- - llvm_targets_SystemZ : SystemZ (s390x) CPU target
- - llvm_targets_WebAssembly : WebAssembly backend
- - llvm_targets_XCore : XCore CPU target
- - miri : Install miri, an interpreter for Rust's mid-level intermediate representation (requires USE=nightly)
- - nightly : Enable nightly (UNSTABLE) features
- - rls : Install rls, Rust Language Server (used with IDEs supporting RLS protocol)
- - rust-src : Install rust-src, needed by developer tools and for build-std (cross)
- - rustfmt : Install rustfmt, Rust code formatter
- - system-bootstrap : Bootstrap using installed rust compiler
+ + system-llvm : Use the system LLVM install
- - test : Enable dependencies and/or preparations necessary to run tests (usually controlled by FEATURES=test but can be
toggled independently)
- - verify-sig : Verify upstream signatures on distfiles
- - wasm : Build support for the wasm32-unknown-unknown target

Cheers

Josef.95
Advocate

Joined: 03 Sep 2007
Posts: 4601
Location: Germany

Posted: Sun Jul 03, 2022 7:01 pm Post subject:

@colo-des,
no, the system-llvm use flag is not removed, this use flag is masked for stable versions in /profiles/base/package.use.stable.mask
But yes, it is irritating - `equery uses package` don't show masked use flags.
Best is, look in the ebuild :) ->

example:

grep IUSE `equery w dev-lang/rust-1.59.0`
IUSE="clippy cpu_flags_x86_sse2 debug dist doc miri nightly parallel-compiler rls rustfmt rust-src system-bootstrap system-llvm test wasm ${ALL_LLVM_TARGETS[*]}"

Hu
Administrator

Joined: 06 Mar 2007
Posts: 21842

Posted: Sun Jul 03, 2022 7:09 pm Post subject:

colo-des wrote:

Where did you look? It is locked out by package.use.stable.mask:

profiles/base/package.use.stable.mask:

# Georgy Yakovlev <gyakovlev@gentoo.org> (2019-05-10)
# needs llvm slots which are not stable #678908
# also prone to weird compilation failures
# masking this for now, will readjust as situation changes
>=dev-lang/rust-1.34 system-llvm

colo-des wrote:

However, you could try to force it to be activated by creating the file /etc/portage/profile/package.use.force/rust with this content:

Note that by doing this, you force Portage to offer a configuration that the developers specifically blocked, usually because there are known issues with it.

colo-des
Tux's lil' helper

Joined: 20 May 2011
Posts: 97

Posted: Sun Jul 03, 2022 10:36 pm Post subject:

Quote:

Hu: Where did you look? It is locked out by package.use.stable.mask:

Hoo thanks you, I had looked and had never seen it.

Quote:

Hu: Note that by doing this, you force Portage to offer a configuration that the developers specifically blocked, usually because there are known issues with it.

I do not have it forced to enable system-llvm in /etc/portage/profile/package.use.force/ and I could always enable it from package.use, I tried everything there was to try and the error was always the same:

Code:

gmake: *** [client.mk:65: build] Error 2

The only way was to enable system-llvm in package.use and there I compiled firefox without problems, so it worked for me so I tried to help with my experience in this thread.

I'm seeing things changed from 1.59 to 1.60

Code:

$ cd ~/adm
$ wget https://gitweb.gentoo.org/repo/gentoo.git/plain/dev-lang/rust/rust-1.60.0.ebuild
$ meld /usr/portage/dev-lang/rust/rust-1.59.0.ebuild ~/adm/rust-1.60.0.ebuild

These are the "mains" changes:

Code:

1.59 1.60
IUSE="" versus IUSE="profiler"
local M=4096 versus local M=8192
profiler = false versus profiler = $(toml_usex profiler)

I'll investigate what $(toml_usex profiler) does.
Cheers

sam_
Developer

Joined: 14 Aug 2020
Posts: 1707

Posted: Mon Jul 04, 2022 12:38 am Post subject:

I doubt any of this is related to system-llvm. As per the bug that's been linked repeatedly, if anything, it's to do with newer Clang. A workaround has been mentioned here & in that bug.

sleepingsun
Guru
Guru

Joined: 03 May 2006
Posts: 458
Location: Bosnia

Posted: Thu Jul 07, 2022 11:43 am Post subject:

Still no luck for firefox

Also can t found this

Code:

profiles/base/package.use.stable.mask

I just have this

Code:

make.conf package.mask package.use repos.conf
make.profile package.unmask profile savedconfig

_________________
Gentoo is Rocks

jplx-gnt2
n00b
n00b

Joined: 27 Jul 2022
Posts: 10
Location: San Jose, California

Posted: Wed Jul 27, 2022 8:29 pm Post subject: Firefox failure to emerge

I have the same problem on two different computers and filed bug #861536.

jplx-gnt2
n00b
n00b

Joined: 27 Jul 2022
Posts: 10
Location: San Jose, California

Posted: Fri Jul 29, 2022 12:10 am Post subject:

Bug # 861536 (that I filed) has been changed to a duplicate of bug #838373.

Josef.95
Advocate

Joined: 03 Sep 2007
Posts: 4601
Location: Germany

Posted: Fri Jul 29, 2022 9:05 pm Post subject:

Please try the workaround from https://bugs.gentoo.org/838373 it should work.

Display posts from previous:

	Gentoo Forums Forum Index Portage & Programming	All times are GMT Goto page 1, 2 Next
Page 1 of 2

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Copyright 2001-2024 Gentoo Foundation, Inc. Designed by Kyle Manna © 2003; Style derived from original subSilver theme. | Hosting by Gossamer Threads Inc. © | Powered by phpBB 2.0.23-gentoo-p11 © 2001, 2002 phpBB Group
Privacy Policy