Bug 927649 – emerge doesn't seem to differentiate between x86_64 and x86_64-v3

• Status: UNCONFIRMED
• Product: Portage Development

[Description 2857 2024-03-23 20:54:23 UTC]

Trying to migrate from 17.1 to 23.0 as per the guide. Having previously specified x86_64-v3 in /etc/portage/binrepos.conf/gentoobinhost.conf (I'm running Xeon Haswell), I've updated it to a more generic x86_64, however, this didn't help:

# emerge --ask --oneshot --getbinpkg sys-devel/binutils

Local copy of remote index is up-to-date and will be used.

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

Calculating dependencies... done!
Dependency resolution took 1.42 s (backtrack: 0/20).

[binary     U  ] sys-libs/glibc-2.38-r10-1 [2.37-r7] USE="cet*" 
[binary     U  ] sys-devel/binutils-2.41-r5-1 [2.41-r2] USE="cet* zstd*" 

Would you like to merge these packages? [Yes/No] y

>>> Running pre-merge checks for sys-libs/glibc-2.38-r10
 * glibc-2.38-r10-7.gpkg.tar MD5 SHA1 size ;-) ...                       [ ok ]
 * After upgrading glibc, please restart all running processes.
 * Be sure to include init (telinit u) or systemd (systemctl daemon-reexec).
 * Alternatively, reboot your system.
 * (See bug #660556, bug #741116, bug #823756, etc)

>>> Emerging binary (1 of 2) sys-libs/glibc-2.38-r10::gentoo
 * glibc-2.38-r10-7.gpkg.tar MD5 SHA1 size ;-) ...                       [ ok ]
>>> Extracting info
>>> Extracting sys-libs/glibc-2.38-r10

>>> Installing (1 of 2) sys-libs/glibc-2.38-r10::gentoo
 * Checking general environment sanity.
x86_64-pc-linux-gnu-gcc -m64 -pipe -march=x86-64-v3 -O2 -Wl,-O1 -Wl,--as-needed -Wl,-z,pack-relative-relocs -pipe -march=x86-64-v3 -O2   -Wl,-O1 -Wl,--as-needed -Wl,-z,pack-relative-relocs  glibc-test.c   -o glibc-test
 * Defaulting /etc/host.conf:multi to on
 * Last-minute run tests with ./ld-linux-x86-64.so.2 in /lib64 ...
/var/tmp/portage/sys-libs/glibc-2.38-r10/temp/environment: line 2329:  5097 Illegal instruction     LC_ALL=C ${newldso} --library-path . ${x} > /dev/null
 * ERROR: sys-libs/glibc-2.38-r10::gentoo failed (preinst phase):
 *   simple run test (/usr/bin/cal) failed
 * 
 * Call stack:
 *     ebuild.sh, line  136:  Called pkg_preinst
 *   environment, line 2814:  Called glibc_sanity_check
 *   environment, line 2342:  Called die
 * The specific snippet of code:
 *           LC_ALL=C ${newldso} --library-path . ${x} > /dev/null || die "simple run test (${x}) failed";
 * 
 * If you need support, post the output of `emerge --info '=sys-libs/glibc-2.38-r10::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.38-r10::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.38-r10/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.38-r10/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-libs/glibc-2.38-r10/image/lib64'
 * S: '/var/tmp/portage/sys-libs/glibc-2.38-r10/work/glibc-2.38'
!!! FAILED preinst: 1

>>> Completed (1 of 2) sys-libs/glibc-2.38-r10::gentoo

>>> Failed to install sys-libs/glibc-2.38-r10, Log file:

>>>  '/var/tmp/portage/sys-libs/glibc-2.38-r10/temp/build.log'

 * Messages for package sys-libs/glibc-2.38-r10:

 * After upgrading glibc, please restart all running processes.
 * Be sure to include init (telinit u) or systemd (systemctl daemon-reexec).
 * Alternatively, reboot your system.
 * (See bug #660556, bug #741116, bug #823756, etc)

 * Messages for package sys-libs/glibc-2.38-r10:

 * ERROR: sys-libs/glibc-2.38-r10::gentoo failed (preinst phase):
 *   simple run test (/usr/bin/cal) failed
 * 
 * Call stack:
 *     ebuild.sh, line  136:  Called pkg_preinst
 *   environment, line 2814:  Called glibc_sanity_check
 *   environment, line 2342:  Called die
 * The specific snippet of code:
 *           LC_ALL=C ${newldso} --library-path . ${x} > /dev/null || die "simple run test (${x}) failed";
 * 
 * If you need support, post the output of `emerge --info '=sys-libs/glibc-2.38-r10::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.38-r10::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.38-r10/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.38-r10/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-libs/glibc-2.38-r10/image/lib64'
 * S: '/var/tmp/portage/sys-libs/glibc-2.38-r10/work/glibc-2.38'

 * GNU info directory index is up-to-date.



Reproducible: Always

[Comment 1 2857 2024-03-23 20:54:39 UTC]

Created attachment 888335 [details]
/proc/cpuinfo

[Comment 2 Sam James 2024-03-23 20:55:04 UTC]

I think you'd have to purge any old binpkgs in /var/cache/binpkgs.

[Comment 3 2857 2024-03-23 20:57:56 UTC]

Yes, I did it and it helped... still I somehow was under the impression this subarch info is specified in gpkg.

[Comment 4 2857 2024-03-23 20:59:19 UTC]

Not sure if it's a bug or not though. Anyway thanks for the quick help!