| View previous topic :: View next topic |
| Author |
Message |
linuxies
n00b
Joined: 18 Jan 2022
Posts: 9
|
 Posted: Wed Jan 19, 2022 3:51 pm Post subject: emerge --ask --verbose --update --deep --newuse @world error |
 |
|
whenever i try to input --ask --verbose --update --deep --newuse @world the following comes up:
| Code: | # emerge --ask --verbose --update --deep --newuse @world
These are the packages that would be merged, in order:
Calculating dependencies
* IMPORTANT: 12 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
.... done!
!!! The ebuild selected to satisfy "~dev-lang/rust-1.56.1[rustfmt?,abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?]" has unmet requirements.
- dev-lang/rust-1.56.1::gentoo USE="-clippy -debug -doc (-miri) (-nightly) (-parallel-compiler) -rls -rust-src -rustfmt (-system-bootstrap) (-system-llvm) -test -verify-sig -wasm" CPU_FLAGS_X86="-sse2" LLVM_TARGETS="(X86) -AArch64 -AMDGPU -ARM -AVR -BPF -Hexagon -Lanai -MSP430 -Mips -NVPTX -PowerPC -RISCV -Sparc -SystemZ -WebAssembly -XCore"
The following REQUIRED_USE flag constraints are unsatisfied:
x86? ( cpu_flags_x86_sse2 )
The above constraints are a subset of the following complete expression:
any-of ( llvm_targets_AArch64 llvm_targets_AMDGPU llvm_targets_ARM llvm_targets_AVR llvm_targets_BPF llvm_targets_Hexagon llvm_targets_Lanai llvm_targets_Mips llvm_targets_MSP430 llvm_targets_NVPTX llvm_targets_PowerPC llvm_targets_RISCV llvm_targets_Sparc llvm_targets_SystemZ llvm_targets_WebAssembly llvm_targets_X86 llvm_targets_XCore ) miri? ( nightly ) parallel-compiler? ( nightly ) rls? ( rust-src ) test? ( llvm_targets_AArch64 llvm_targets_AMDGPU llvm_targets_ARM llvm_targets_AVR llvm_targets_BPF llvm_targets_Hexagon llvm_targets_Lanai llvm_targets_Mips llvm_targets_MSP430 llvm_targets_NVPTX llvm_targets_PowerPC llvm_targets_RISCV llvm_targets_Sparc llvm_targets_SystemZ llvm_targets_WebAssembly llvm_targets_X86 llvm_targets_XCore ) wasm? ( llvm_targets_WebAssembly ) x86? ( cpu_flags_x86_sse2 )
(dependency required by "virtual/rust-1.56.1::gentoo" [ebuild])
(dependency required by "dev-lang/spidermonkey-78.15.0::gentoo" [ebuild])
(dependency required by "sys-auth/polkit-0.120-r1::gentoo" [ebuild])
(dependency required by "sys-auth/polkit-qt-0.114.0::gentoo" [ebuild])
(dependency required by "kde-frameworks/kauth-5.88.0::gentoo" [ebuild])
(dependency required by "kde-frameworks/kconfigwidgets-5.88.0-r1::gentoo" [ebuild])
(dependency required by "kde-frameworks/kiconthemes-5.88.0-r1::gentoo" [ebuild])
(dependency required by "kde-plasma/polkit-kde-agent-5.23.5::gentoo" [ebuild])
|
what do i need to do in order to fix the REQUIRED_USE flag? |
|
| Back to top |
|
 |
grknight
Retired Dev
Joined: 20 Feb 2015
Posts: 1659
|
| Posted: Wed Jan 19, 2022 4:15 pm Post subject: |
|
|
Unless this CPU is missing SSE2 (i.e. predates Pentium 4), then the best thing to do is to install app-portage/cpuid2cpuflags and then run:
| Code: | | mkdir -p /etc/portage/package.use && echo "*/* $(cpuid2cpuflags)" > /etc/portage/package.use/00cpuflags |
|
|
| Back to top |
|
|
linuxies
n00b
Joined: 18 Jan 2022
Posts: 9
|
| Posted: Wed Jan 19, 2022 5:14 pm Post subject: |
|
|
| grknight wrote: | Unless this CPU is missing SSE2 (i.e. predates Pentium 4), then the best thing to do is to install app-portage/cpuid2cpuflags and then run:
| Code: | | mkdir -p /etc/portage/package.use && echo "*/* $(cpuid2cpuflags)" > /etc/portage/package.use/00cpuflags |
|
emerge wont let me install cpuid2cpuflags:
| Code: | # emerge app-portage/cpuid2cpuflags
Calculating dependencies
* IMPORTANT: 12 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
.... done!
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) app-portage/cpuid2cpuflags-11::gentoo
* cpuid2cpuflags-11.tar.bz2 BLAKE2B SHA512 size ;-) ... [ ok ]
>>> Unpacking source...
>>> Unpacking cpuid2cpuflags-11.tar.bz2 to /var/tmp/portage/app-portage/cpuid2cpuflags-11/work
>>> Source unpacked in /var/tmp/portage/app-portage/cpuid2cpuflags-11/work
>>> Preparing source in /var/tmp/portage/app-portage/cpuid2cpuflags-11/work/cpuid2cpuflags-11 ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/app-portage/cpuid2cpuflags-11/work/cpuid2cpuflags-11 ...
./configure --prefix=/usr --build=i486-pc-linux-gnu --host=i486-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking --disable-silent-rules --docdir=/usr/share/doc/cpuid2cpuflags-11 --htmldir=/usr/share/doc/cpuid2cpuflags-11/html --libdir=/usr/lib
checking for a BSD-compatible install... /usr/lib/portage/python3.9/ebuild-helpers/xattr/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking for i486-pc-linux-gnu-gcc... i486-pc-linux-gnu-gcc
checking whether the C compiler works... no
configure: error: in `/var/tmp/portage/app-portage/cpuid2cpuflags-11/work/cpuid2cpuflags-11':
configure: error: C compiler cannot create executables
See `config.log' for more details
!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/app-portage/cpuid2cpuflags-11/work/cpuid2cpuflags-11/config.log
* ERROR: app-portage/cpuid2cpuflags-11::gentoo failed (configure phase):
* econf failed
*
* Call stack:
* ebuild.sh, line 127: Called src_configure
* environment, line 448: Called default
* phase-functions.sh, line 858: Called default_src_configure
* phase-functions.sh, line 893: Called __eapi2_src_configure
* phase-helpers.sh, line 828: Called econf
* phase-helpers.sh, line 711: Called __helpers_die 'econf failed'
* isolated-functions.sh, line 112: Called die
* The specific snippet of code:
* die "$@"
*
* If you need support, post the output of `emerge --info '=app-portage/cpuid2cpuflags-11::gentoo'`,
* the complete build log and the output of `emerge -pqv '=app-portage/cpuid2cpuflags-11::gentoo'`.
* The complete build log is located at '/var/tmp/portage/app-portage/cpuid2cpuflags-11/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/app-portage/cpuid2cpuflags-11/temp/environment'.
* Working directory: '/var/tmp/portage/app-portage/cpuid2cpuflags-11/work/cpuid2cpuflags-11'
* S: '/var/tmp/portage/app-portage/cpuid2cpuflags-11/work/cpuid2cpuflags-11'
>>> Failed to emerge app-portage/cpuid2cpuflags-11, Log file:
>>> '/var/tmp/portage/app-portage/cpuid2cpuflags-11/temp/build.log'
* Messages for package app-portage/cpuid2cpuflags-11:
* ERROR: app-portage/cpuid2cpuflags-11::gentoo failed (configure phase):
* econf failed
*
* Call stack:
* ebuild.sh, line 127: Called src_configure
* environment, line 448: Called default
* phase-functions.sh, line 858: Called default_src_configure
* phase-functions.sh, line 893: Called __eapi2_src_configure
* phase-helpers.sh, line 828: Called econf
* phase-helpers.sh, line 711: Called __helpers_die 'econf failed'
* isolated-functions.sh, line 112: Called die
* The specific snippet of code:
* die "$@"
*
* If you need support, post the output of `emerge --info '=app-portage/cpuid2cpuflags-11::gentoo'`,
* the complete build log and the output of `emerge -pqv '=app-portage/cpuid2cpuflags-11::gentoo'`.
* The complete build log is located at '/var/tmp/portage/app-portage/cpuid2cpuflags-11/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/app-portage/cpuid2cpuflags-11/temp/environment'.
* Working directory: '/var/tmp/portage/app-portage/cpuid2cpuflags-11/work/cpuid2cpuflags-11'
* S: '/var/tmp/portage/app-portage/cpuid2cpuflags-11/work/cpuid2cpuflags-11' |
|
|
| Back to top |
|
|
grknight
Retired Dev
Joined: 20 Feb 2015
Posts: 1659
|
| Posted: Wed Jan 19, 2022 5:23 pm Post subject: |
|
|
| linuxies wrote: | | grknight wrote: | Unless this CPU is missing SSE2 (i.e. predates Pentium 4), then the best thing to do is to install app-portage/cpuid2cpuflags and then run:
| Code: | | mkdir -p /etc/portage/package.use && echo "*/* $(cpuid2cpuflags)" > /etc/portage/package.use/00cpuflags |
|
emerge wont let me install cpuid2cpuflags:
| Code: | checking for i486-pc-linux-gnu-gcc... i486-pc-linux-gnu-gcc
checking whether the C compiler works... no
configure: error: in `/var/tmp/portage/app-portage/cpuid2cpuflags-11/work/cpuid2cpuflags-11':
configure: error: C compiler cannot create executables
See `config.log' for more details
|
|
99% of the time on new installs, this error means a typo in CFLAGS or COMMON_FLAGS inside the make.conf file.
On a side note, why was the i486 stage3 used? This is very limited for incredibly old CPUs. What CPU is this VM (noted from last post) running with? |
|
| Back to top |
|
|
linuxies
n00b
Joined: 18 Jan 2022
Posts: 9
|
| Posted: Wed Jan 19, 2022 6:20 pm Post subject: |
|
|
| grknight wrote: | | linuxies wrote: | | grknight wrote: | Unless this CPU is missing SSE2 (i.e. predates Pentium 4), then the best thing to do is to install app-portage/cpuid2cpuflags and then run:
| Code: | | mkdir -p /etc/portage/package.use && echo "*/* $(cpuid2cpuflags)" > /etc/portage/package.use/00cpuflags |
|
emerge wont let me install cpuid2cpuflags:
| Code: | checking for i486-pc-linux-gnu-gcc... i486-pc-linux-gnu-gcc
checking whether the C compiler works... no
configure: error: in `/var/tmp/portage/app-portage/cpuid2cpuflags-11/work/cpuid2cpuflags-11':
configure: error: C compiler cannot create executables
See `config.log' for more details
|
|
99% of the time on new installs, this error means a typo in CFLAGS or COMMON_FLAGS inside the make.conf file.
On a side note, why was the i486 stage3 used? This is very limited for incredibly old CPUs. What CPU is this VM (noted from last post) running with? |
thank you, knowing myself it is probably a typo.
the vm uses my own cpu on this laptop, which is a intel i7-8565U, and i used the 1st safe flag in the handbook of intel, should i have replaced it with another? |
|
| Back to top |
|
|
grknight
Retired Dev
Joined: 20 Feb 2015
Posts: 1659
|
| Posted: Wed Jan 19, 2022 6:28 pm Post subject: |
|
|
| linuxies wrote: | | grknight wrote: |
99% of the time on new installs, this error means a typo in CFLAGS or COMMON_FLAGS inside the make.conf file.
On a side note, why was the i486 stage3 used? This is very limited for incredibly old CPUs. What CPU is this VM (noted from last post) running with? |
thank you, knowing myself it is probably a typo.
the vm uses my own cpu on this laptop, which is a intel i7-8565U, and i used the 1st safe flag in the handbook of intel, should i have replaced it with another? |
How about sharing your make.conf file? This will help us.
In all honesty, this should have been an amd64 install for 64-bit support, or at the very least, an i686 stage3 for 32-bit only. It is possible that the i486 stage3 will hold things back. |
|
| Back to top |
|
|
linuxies
n00b
Joined: 18 Jan 2022
Posts: 9
|
| Posted: Wed Jan 19, 2022 6:41 pm Post subject: |
|
|
| grknight wrote: | | linuxies wrote: | | grknight wrote: |
99% of the time on new installs, this error means a typo in CFLAGS or COMMON_FLAGS inside the make.conf file.
On a side note, why was the i486 stage3 used? This is very limited for incredibly old CPUs. What CPU is this VM (noted from last post) running with? |
thank you, knowing myself it is probably a typo.
the vm uses my own cpu on this laptop, which is a intel i7-8565U, and i used the 1st safe flag in the handbook of intel, should i have replaced it with another? |
How about sharing your make.conf file? This will help us.
In all honesty, this should have been an amd64 install for 64-bit support, or at the very least, an i686 stage3 for 32-bit only. It is possible that the i486 stage3 will hold things back. |
I wouldn't mind installing it in amd64, its just whenever I did that I had a problem with chroot with /bin/bash, so I switched over using to x86, which seemed to fix the problem, but i'm definitely willing to do it in amd64, even though my system is 86x, would it still work? |
|
| Back to top |
|
|
grknight
Retired Dev
Joined: 20 Feb 2015
Posts: 1659
|
| Posted: Wed Jan 19, 2022 6:49 pm Post subject: |
|
|
| linuxies wrote: | | I wouldn't mind installing it in amd64, its just whenever I did that I had a problem with chroot with /bin/bash, so I switched over using to x86, which seemed to fix the problem, but i'm definitely willing to do it in amd64, even though my system is 86x, would it still work? |
An i7 is amd64 aka x86_64 for sure. Just starting from a 64-bit environment into an 64-bit ISO and later a 64-bit install is crucial.
If the initial environment is 32-bit, then i686 is the best stage3.
No matter what, the make.conf and config.log will tell us what is wrong if you keep going with the current setup. |
|
| Back to top |
|
|
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21624
|
| Posted: Thu Jan 20, 2022 3:01 am Post subject: |
|
|
| Please develop the habit of reading the full output of failed commands, and following the advice therein. In particular, you posted output where Portage specifically asked you to share certain log files. You have not yet shared those, so we can only guess at how things failed. |
|
| Back to top |
|
|
linuxies
n00b
Joined: 18 Jan 2022
Posts: 9
|
| Posted: Thu Jan 20, 2022 9:55 pm Post subject: |
|
|
| grknight wrote: | | linuxies wrote: | | I wouldn't mind installing it in amd64, its just whenever I did that I had a problem with chroot with /bin/bash, so I switched over using to x86, which seemed to fix the problem, but i'm definitely willing to do it in amd64, even though my system is 86x, would it still work? |
An i7 is amd64 aka x86_64 for sure. Just starting from a 64-bit environment into an 64-bit ISO and later a 64-bit install is crucial.
If the initial environment is 32-bit, then i686 is the best stage3.
No matter what, the make.conf and config.log will tell us what is wrong if you keep going with the current setup. |
i have decided to follow your advice and make a new install and make a 86_64 installation, its going much more smoother, and the only issue so far that is stopping my progress for installing is installing the genkernel. I output this command:
After it takes a while to compile, I run to an error:
| Code: | ERROR: compile_modules(): compile_generic() failed to compile the "modules_install" target!
Please consult 'var/log/genkernel.log for more information and any errors that were reported above.'
|
When visiting the log using nano var/log/genkernel.log I don't see any errors as it is quite long, is there a particular part that I need to check for errors? I'm really sorry for flooding this forum with my threads and wasting your time |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54234
Location: 56N 3W
|
| Posted: Fri Jan 21, 2022 7:17 pm Post subject: |
|
|
linuxies,
We all remember our first installs. You are learning and gaining experience.
Your helpers remember when they were where you are today.
For most logs, use wgetpaste to put them on a pastebin site, then post the link.
Its much easier for us to find the error ant post a quote to explain it you you and others finding the topic in the future, that it is to guess where to look.
You will need to install wgetpaste if you don't have it.
--edit --
| Code: | | ... failed to compile the "modules_install" target! |
modules_install does not actually compile anything. It copies the kernel modules from the build location to where the kernel will find them.
Is your filesystem full ?
What does and show.
You need both free space and free i-nodes for the copy.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
|
|
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
|
|
Installing Gentoo
