View previous topic :: View next topic |
Author |
Message |
solamour l33t
Joined: 21 Dec 2004 Posts: 726 Location: San Diego, CA
|
Posted: Mon Sep 16, 2024 12:00 am Post subject: [Solved] CPU ISA level is lower than required |
|
|
I'm getting "CPU ISA level is lower than required" when I run these commands on a freshly set up machine.
Code: | $ gtk-update-icon-cache
gtk-update-icon-cache: CPU ISA level is lower than required
$ vncpasswd
vncpasswd: CPU ISA level is lower than required |
There might be other commands that have the same problem, but so far those are the only ones I encountered. It might be different from "glibc-2.39-r6 CPU ISA level is lower than required" (https://forums.gentoo.org/viewtopic-t-1169200.html), because this time, it's x86_64 with a slightly modern CPU. I'd appreciate any suggestions on how to resolve.
Code: | Portage 3.0.65 (python 3.12.3-final-0, default/linux/amd64/23.0, gcc-13, glibc-2.39-r6, 6.6.47-gentoo x86_64)
=================================================================
System uname: Linux-6.6.47-gentoo-x86_64-AMD_A6-1450_APU_with_Radeon-TM-_HD_Graphics-with-glibc2.39
KiB Mem: 7560124 total, 7281668 free
KiB Swap: 0 total, 0 free
Timestamp of repository gentoo: Sat, 14 Sep 2024 10:00:00 +0000
Head commit of repository gentoo: e577e4b6171fc7e2601944aabb18325a2a017f3e
sh bash 5.2_p26-r6
ld GNU ld (Gentoo 2.42 p3) 2.42.0
app-misc/pax-utils: 1.3.7::gentoo
app-shells/bash: 5.2_p26-r6::gentoo
dev-build/autoconf: 2.71-r7::gentoo
dev-build/automake: 1.16.5-r2::gentoo
dev-build/libtool: 2.4.7-r4::gentoo
dev-build/make: 4.4.1-r1::gentoo
dev-build/meson: 1.5.1::gentoo
dev-lang/perl: 5.40.0::gentoo
dev-lang/python: 3.12.3-r1::gentoo
sys-apps/baselayout: 2.15::gentoo
sys-apps/openrc: 0.54.2::gentoo
sys-apps/sandbox: 2.39::gentoo
sys-devel/binutils: 2.42-r1::gentoo
sys-devel/binutils-config: 5.5::gentoo
sys-devel/gcc: 13.3.1_p20240614::gentoo
sys-devel/gcc-config: 2.11::gentoo
sys-devel/llvm: 18.1.8-r1::gentoo
sys-kernel/linux-headers: 6.6-r1::gentoo (virtual/os-headers)
sys-libs/glibc: 2.39-r6::gentoo
Repositories:
gentoo
location: /var/db/repos/gentoo
sync-type: rsync
sync-uri: rsync://gentoo/gentoo-portage
priority: -1000
volatile: False
sync-rsync-verify-jobs: 1
sync-rsync-verify-max-age: 3
sync-rsync-extra-opts:
sync-rsync-verify-metamanifest: yes
Binary Repositories:
gentoobinhost
priority: 1
sync-uri: ssh://solamour@gentoo/var/cache/binpkgs
ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="@FREE"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=native -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d"
CXXFLAGS="-march=native -O2 -pipe"
DISTDIR="/var/cache/distfiles"
ENV_UNSET="CARGO_HOME DBUS_SESSION_BUS_ADDRESS DISPLAY GDK_PIXBUF_MODULE_FILE GOBIN GOPATH PERL5LIB PERL5OPT PERLPREFIX PERL_CORE PERL_MB_OPT PERL_MM_OPT XAUTHORITY XDG_CACHE_HOME XDG_CONFIG_HOME XDG_DATA_HOME XDG_RUNTIME_DIR XDG_STATE_HOME"
FCFLAGS="-march=native -O2 -pipe"
FEATURES="assume-digests binpkg-docompress binpkg-dostrip binpkg-logs binpkg-multi-instance buildpkg-live config-protect-if-modified distlocks ebuild-locks fixlafiles getbinpkg ipc-sandbox merge-sync merge-wait multilib-strict network-sandbox news parallel-fetch pid-sandbox pkgdir-index-trusted preserve-libs protect-owned qa-unresolved-soname-deps sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr"
FFLAGS="-march=native -O2 -pipe"
GENTOO_MIRRORS="http://distfiles.gentoo.org"
LANG="C.UTF8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,-z,pack-relative-relocs"
LEX="flex"
MAKEOPTS="-j4"
PKGDIR="/var/cache/binpkgs"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --exclude=/.git"
PORTAGE_TMPDIR="/var/tmp"
SHELL="/bin/bash"
USE="acl amd64 bzip2 cet crypt elogind gdbm iconv ipv6 libtirpc multilib ncurses nls openmp pam pcre readline seccomp ssl test-rust unicode xattr zlib" ABI_X86="64" ADA_TARGET="gcc_12" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_anon authn_dbm authn_file authz_dbm authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir env expires ext_filter file_cache filter headers include info log_config logio mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="karbon sheets words" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="mmx mmxext sse sse2" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock greis isync itrax mtk3301 ntrip navcom oceanserver oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 tsip tripmate tnt ublox" GRUB_PLATFORMS="efi-64" GUILE_SINGLE_TARGET="3-0" GUILE_TARGETS="3-0" INPUT_DEVICES="libinput" KERNEL="linux" LCD_DEVICES="bayrad cfontz glk hd44780 lb216 lcdm001 mtxorb text" LUA_SINGLE_TARGET="lua5-1" LUA_TARGETS="lua5-1" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php8-2" POSTGRES_TARGETS="postgres15" PYTHON_SINGLE_TARGET="python3_12" PYTHON_TARGETS="python3_12" RUBY_TARGETS="ruby31 ruby32" VIDEO_CARDS="amdgpu radeonsi" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipp2p iface geoip fuzzy condition tarpit sysrq proto logmark ipmark dhcpmac delude chaos account"
Unset: ADDR2LINE, AR, ARFLAGS, AS, ASFLAGS, CC, CCLD, CONFIG_SHELL, CPP, CPPFLAGS, CTARGET, CXX, CXXFILT, ELFEDIT, EMERGE_DEFAULT_OPTS, EXTRA_ECONF, F77FLAGS, FC, GCOV, GPROF, INSTALL_MASK, LC_ALL, LD, LFLAGS, LIBTOOL, LINGUAS, MAKE, MAKEFLAGS, NM, OBJCOPY, OBJDUMP, PORTAGE_BINHOST, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PYTHONPATH, RANLIB, READELF, RUSTFLAGS, SIZE, STRINGS, STRIP, YACC, YFLAGS |
__
sol
Last edited by solamour on Wed Sep 18, 2024 7:43 pm; edited 2 times in total |
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 22618
|
Posted: Mon Sep 16, 2024 12:18 am Post subject: |
|
|
Your topic link does not work, because you included a trailing comma in it. Consider using [topic] rather than a bare URL.
Your emerge --info appears to be lightly mangled due to a bad interaction with your terminal and/or tmux. Consider using xclip to put it on the clipboard, or save it to a file and then use an editor to copy it into the forum post.
I see you have binary packages enabled, and pull them from a private binhost. With what -march settings does it build packages? If it also uses -march=native, are all client machines at least as capable as the binhost? Are the broken packages locally built or did they come from the binhost? |
|
Back to top |
|
|
Genone Retired Dev
Joined: 14 Mar 2003 Posts: 9608 Location: beyond the rim
|
Posted: Mon Sep 16, 2024 1:42 am Post subject: |
|
|
While the cause is probably different, the actual problem is the same: For some unknown reason those binaries apparently require the v3 instruction set while your CPU only supports v2. But as Hu pointed out, you need to provide information about where and how those packages (and anything they depend on) were built. |
|
Back to top |
|
|
solamour l33t
Joined: 21 Dec 2004 Posts: 726 Location: San Diego, CA
|
Posted: Mon Sep 16, 2024 3:46 am Post subject: |
|
|
Thanks for pointing out the post's formatting. I made the necessary changes.
The host that builds the binary packages is slightly more modern than the one that is using the binary packages. They both use COMMON_FLAGS="-march=native -O2 -pipe", and I suspect that might have something to do with the problem.
Before I rebuild everything locally, which will most likely take a l...o...n...g time, what would be the minimal set of packages I should try rebuilding?
__
sol |
|
Back to top |
|
|
solamour l33t
Joined: 21 Dec 2004 Posts: 726 Location: San Diego, CA
|
Posted: Wed Sep 18, 2024 7:43 pm Post subject: |
|
|
Turned out the binhost I was using had the binary for "x86-64-v3", while the target machine supported only "x86-64-v2".
[binhost]
Code: | $ ld.so --help
...
Subdirectories of glibc-hwcaps directories, in priority order:
x86-64-v4
x86-64-v3 (supported, searched)
x86-64-v2 (supported, searched)
|
[target]
Code: | $ ld.so --help
...
Subdirectories of glibc-hwcaps directories, in priority order:
x86-64-v4
x86-64-v3
x86-64-v2 (supported, searched)
|
I thought only USE flag mattered when using binary packages, but COMMON_FLAGS definitely is more important. Thanks everyone for taking time to share your insights and suggestions.
__
sol |
|
Back to top |
|
|
logrusx Advocate
Joined: 22 Feb 2018 Posts: 2401
|
Posted: Thu Sep 19, 2024 3:37 am Post subject: |
|
|
solamour wrote: | They both use COMMON_FLAGS="-march=native -O2 -pipe", and I suspect that might have something to do with the problem. |
Of course it does. Your more modern computer is producing binaries for itself. Decrease the ISA level for your binhost or use buildroot for binary packages.
Best Regards,
Georgi |
|
Back to top |
|
|
solamour l33t
Joined: 21 Dec 2004 Posts: 726 Location: San Diego, CA
|
Posted: Sat Sep 21, 2024 8:38 pm Post subject: |
|
|
Kinda wish that emerge would flag it, just as it does for "USE", so that if there is a chance I might end up with a wonky system, it would build the packages locally rather than blindly accepting what binhost provides.
__
sol |
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 22618
|
Posted: Sat Sep 21, 2024 9:42 pm Post subject: |
|
|
The problem is that some CFLAGS differences can be harmless, such as extra warnings, or a -mtune different from what you would like. Others, as you found, are quite important. Portage would need to have a recognizer that could categorize flags as mismatch-safe or mismatch-unsafe. |
|
Back to top |
|
|
Genone Retired Dev
Joined: 14 Mar 2003 Posts: 9608 Location: beyond the rim
|
Posted: Sun Sep 22, 2024 2:22 am Post subject: |
|
|
solamour wrote: | Kinda wish that emerge would flag it, just as it does for "USE", so that if there is a chance I might end up with a wonky system, it would build the packages locally rather than blindly accepting what binhost provides.l |
The complexity involved to do that properly without any significant downsides is not really feasable.
Never been a big fan of march=native for this very reason |
|
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
|
|