[solved] Profile upgrade from 17.1 to 23: error rebuild gcc

[guerro]

Following the upgrade guide, at point 9:

[guerro]

Found the problem:
when rebuild, there is a new USE flag: cet, which is added to glibc (dependency excluded from rebuild as indicated by guide) too.

I think that to use new cet USE flag in gcc, glibc has to be compiled with that flag too.

Now I compiled gcc without cet USE flag (and compile go fine), then I'll compile glibc (with cet USE flag) and then rebuild gcc[/b] with cet USE flag.
_________________
(.(*. .*).)
.. G u e r r o ..
(.(.* *.).)

[dilfridge]

Please try again with "-march=native" either removed or replaced with a specific setting for a (your) CPU.

If it buils then, it's probably a duplicate of https://bugs.gentoo.org/908523

[guerro]

[Vrenn]

ok, but where to find the List of supported profiles of your cpu?
Got it: https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html#index-march-13
_________________
With nice greetings
Vrenn

[Vrenn]

[dilfridge]

[pietinger]

Same problem here with an Intel RaptorLake, and COMMON_FLAGS="-march=native -O2 -pipe" already (all the time) in make.conf.

I was on (a split-usr) profile: 17.1-PLASMA + No-Multilib and in step: "Nr. 6. Select the 23.0 profile" I made a change (only first line) in my local profile to:

[grknight]

[pietinger]

[pietinger]

Update: After changing COMMON_FLAGS to raptorlake in my make.conf the emerge of gcc was successful

[kimchi_sg]

I hit the same problem as original post.

Removed -march totally and compiled gcc - success.
Re-added -march=native and re-compiled gcc - still failed.
Left in -march=native and proceeded to next step, emerge glibc.

Now doing emerge -e @world...

EDIT: emerge -e @world with -march=native fails again on gcc, same error.

Going to use package.env to workaround this one.

[wynnmc]

Thanks, Dilfridge, changing -march from native worked for me too.

I found app-misc/resolve-march-native very helpful in finding out what should replace native.

[kvada]

I have the problem with gcc but on install phase:

[sam_]

Please emerge --sync. That should be fixed now.

[hujuice]

[jagdpanther]

Two issues:

1. I had the same issue as the OP.

In /etc/protage/make.conf I switched COMMON_FLAGS
from: COMMON_FLAGS="-march=native -O2 -fomit-frame-pointer -pipe"
to: COMMON_FLAGS="-march=raptorlake -O2 -fomit-frame-pointer -pipe"
because of my i9-13900k.

Thanks pietinger for your post.

Because binutils was built with -march=native and I have no idea if
this would cause issues I restarted step 9 of "Profile upgrade to version 23.0
available" news item and rebuild binuitls with the -march=raptorlake also. If
anyone know if this is a good idea or me just being parinoid please let me
know.

2. Then I hit the:

[shimbob]

[kvada]

[hujuice]

Same here.

-march=alderlake is mandatory to build gcc with cet.
_________________
Who hasn't a spine, should have a method.
Chi non ha carattere, deve pur avere un metodo.

[sam_]

That also was fixed (or should've been) yesterday, but it may not have hit your mirrors when you synced.

If you have further issues, please open a new thread and include emerge --info and the build.log. Thanks.

[hujuice]

[e8root]

I remember trying cet USE flag and having build error in the past. I saw it when comparing changes in profiles between 17.1 and 23.0 (as you do...) but decided not to enable it for now it not being critical feature.

GCC failing with -march=native seems like a bug to me. Hopefully it is fixed soon.
If not then I guess I will only need to set -march=raptorlake to GCC?
_________________
Unix Wars - Episode V: AT&T Strikes Back

[hujuice]

[sam_]

What you're seeing above is the latest iteration of the workaround, because we found it couldn't work to forcefully append --param in the eclass. That is, the message was added because of the bug, and it's the best we can do for now.

We've reported the issue to GCC upstream.