- Status Closed
- Percent Complete
- Task Type Bug Report
- Category Packages → Packages: Testing
-
Assigned To
Andreas Baumann - Operating System i686
- Severity Medium
- Priority Medium
- Reported Version
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
Attached to Project: Arch Linux 32
Opened by Erich Eckner - 12.04.2021
Last edited by Erich Eckner - 15.04.2021
Opened by Erich Eckner - 12.04.2021
Last edited by Erich Eckner - 15.04.2021
FS#177 - [gcc] CPU ISA level is lower than required
$ cc –version
cc: CPU ISA level is lower than required
The same happens in a chroot for [staging].
$ pacman -Qo /usr/bin/cc
/usr/bin/cc is owned by gcc 10.2.0-6.0
$ pacman -Q glibc
glibc 2.33-4.0
Does that mean, anything building with gcc is doomed on i686, currently?
Closed by Erich Eckner
15.04.2021 04:50
Reason for closing: Fixed
Additional comments about closing:
15.04.2021 04:50
Reason for closing: Fixed
Additional comments about closing:
fascinating, it works! Thanks!
looks, like there is no problem, when running the i686 chroot inside an x86_64 vm - so our build slaves should be safe.
Still, this poses a problem for me :)
looks, like the crux is in glibc:
interestingly, there is no problem on a similar setup for i486 (versions of gcc and glibc are similar, glibc is 2.33-4.1 instead of 2.33-4.0 - also miraculous, considering, that there is no glibc on the buildlist, currently O.o)
I have on testing:
- i486 glibc 2.33-4.2 (12.4. 20:38)
- i686 glibc 2.33-4.2 (12.4. 22:26)
- pentium4 glibc 2.33-4.2 (12.4. 22:08)
I get on i686 only, i486/pentium4 are ok:
gcc: CPU ISA level is lower than required
So, there has been a rebuild of glibc.
893b1c268abc8822332655865e3d4546025a9b4b (13.2.) is the last commit uptream, so this
didn't trigger a rebuild.
620aea01f148b5141342e77b7ee2a6c4e02fedea (9.2.) last commit in our git, so if nobody
triggered a manual rebuild, I also don't understand why we got a new version.
What I also don't get is that rebuilds suddenly result in a misconfiguration again.
Build for i686 all happen chrooted on 64-bit machines.
I'll build a glibc for i686 manually to see if the problem disappears. Just triggering
a glibc rebuild seems a little bit risky now..
Mmh. Interestingly only gcc shows this problem, not for instance 'file' which has also
been rebuilt.
I did trigger the rebuild of glibc - the differing sub_pkgrel's disturbed my common sense for order.
But the phenomenon you describe is exactly, what I had observed: i486 and pentium4 are ok, i686 is broken. Maybe we need to build i686 glibc on an i686 vm?
What do you mean by "rebuilds suddenly result in a misconfiguration again"?
I meant, that libc_cv_include_x86_isa_level=no has no effect on glibc (and thus creating
the ISA level detection error). But it could also be in gcc itself.
IIRC the ISA level problem was present in i686 and pentium4 last time (when I upgraded
glibc to 2.33), but also not on i486.
I triggered a forced rebuild of gcc, this solves the problem in my experiments.