Il 23/03/24 20:18, Michael ha scritto:
On Saturday, 23 March 2024 19:10:28 GMT you wrote:
Il 23/03/24 19:43, Michael ha scritto:
On Saturday, 23 March 2024 18:29:58 GMT ralfconn wrote:
Il 23/03/24 18:42, Michael ha scritto:
   > I suggest it would be best to take heed of the devs hard work and

read the

   > instructions they have provided instead of winging it:
   >
   > https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_instructio
   > ns

I'm currently running a local merged profile:

# cat /var/db/repos/local/profiles/no-multilib-hardened-desktop/parent
gentoo:default/linux/amd64/17.1/no-multilib/hardened
gentoo:targets/desktop

$ euse -a | grep usr
split-usr           [+  D F ]

I suppose that before step 3 of the wiki I'd need to create a new local
merged profile, e.g.:

#cat
/var/db/repos/local/profiles/23.0-split-usr-no-multilib-hardened-desktop/
par ent gentoo:default/linux/amd64/23.0/split-usr/no-multilib/hardened
gentoo:targets/split-usr/desktop

Does that make sense?

thanks

raf
Update portage and check the profiles offered by 'eselect profile list'.
For example, I can see:

[51]  default/linux/amd64/23.0/split-usr/no-multilib/hardened (stable)

which should provide what you're after.
It's not a 'desktop' profile
I'd think once you emerge/update the desktop environment or main packages you
want, most of the desktop related USE choices will be applied anyway.  In the
first instance I'd select the above profile ([51]), update your toolchain and
try an emerge --pretend of @world to see what USE flag differences remain.  If
this approach leaves you short you can always create your own merged profile
as you had done.

(Due to my mistake the last message was sent to me only instead of the list)

Unfortunately not, the non-desktop profile is very stripped-down compared to the desktop one. There's maybe 20 or more USE flags present in my merged profile that are missing from [51].

In the meanwhile I tried to switch to my merged 23.0 profile, in step 9 binutils updates fine while gcc builds but fails to install with no error message, so for now I'm back to 'merged' 17.1. Tomorrow I'll try to analyze the install log better.

BTW, the only differences comparing emerge --info before and after the switch are:

LDFLAGS="-Wl,-O1 -Wl,--as-needed"

vs

LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,-z,pack-relative-relocs"

and

USE = "cli fortran"

that after the switch disappear in favour of the new ones

USE = "lzma zstd"

(at least, in my 'crooked' local profile)



Reply via email to