[solved] Remaining life of profile 17.1?

pjp · Administrator Joined: 16 Apr 2002 Posts: 20067

With a cursory look at the benefits of 23, my hardware is too old, at least for cet.

Per the euse info for cet on gcc, the benefits require at least Tiger Lake or Zen 3. I have a Phenom and a Kaby Lake. Not being harmful isn't much of a motivation for --emptytree. Similar for -fcf-protection with hardened.

Is 17.1 likely to be EOL sooner than later, or is it likely to be around for multiple years?
_________________
Quis separabit? Quo animo?

grknight · Retired Dev Joined: 20 Feb 2015 Posts: 1702

That's not the only thing that 23.0 does.. 2 other options on sys-devel/gcc become forced:

pjp · Administrator Joined: 16 Apr 2002 Posts: 20067

Thanks. I presumed it was too early, but thought I'd check.
_________________
Quis separabit? Quo animo?

Phoenix591 · Guru Joined: 17 Sep 2007 Posts: 488

https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline shows 17.1 is scheduled to be marked depreciated on 6-6 and then removed 6-6 of next year.

figueroa · Posted: Sat Apr 06, 2024 3:09 am Post subject:

I had my Phenom x3 on "[5] default/linux/x86/17.0/desktop (exp)." Updating to "[28] default/linux/x86/23.0/i686/split-usr/desktop (stable)" posed no issue. The --emptytree ran for about 24 hours, but the machine is on 24/7 anyway. That machine has 8 GB RAM.

This particular machine has been running since 2012. It seemed like a good idea to avoid going obsolete.
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi

pjp · Administrator Joined: 16 Apr 2002 Posts: 20067

@Phoenix591,

Thanks! That gives me a deadline to come up with a solution of some kind.

@figueroa,

I have some sort of issue that I presume is hardware related, maybe overheating. I've had larger packages primarily gcc, clang fail, usually with success on the subsequent attempt. *knock on wood* I haven't seen it in a while. I may not replace the hardware, so I have no replacement plans at this time. That would leave me with laptops, and effectively no system with which to build binaries.

I may try to find a way to build packages in groups, but that seems complicated. So I may end up riding out 17.1 until the end.
_________________
Quis separabit? Quo animo?

NichtDerHans · Tux's lil' helper Joined: 27 Jan 2023 Posts: 138

I can recommend to do the compiling via chroot on a faster computer. I keep my X220 laptop up to date every two weeks. It works very well.

Export the filesystem from the slow PC via NFS in the local Network, mount on the faster PC, chroot to the mountpoint.

NeddySeagoon · Posted: Sat Apr 06, 2024 10:18 am Post subject:

pjp,

If you want to stay on /17.x/ copy the profile to your overlay. Use that instead of the profile from ::gentoo.

Now it gets a bit murky. How much of the profile do you want to keep?
Its possible to copy just parts of a profile too.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

Anon-E-moose · Posted: Sat Apr 06, 2024 11:12 am Post subject:

The easy way is to copy the whole /usr/portage/profile to your local repo, then do eselect profile and point to your local repo.
It only takes up ~3 meg disk space.

I did the whole copy thing back in the 17.0 -> 17.1 days. No problems.
_________________
PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland

pjp · Administrator Joined: 16 Apr 2002 Posts: 20067

@NichtDerHans,

That is the "faster" computer :)

@NeddySeagoon, Anon-E-moose,

The initial concern there is what I'd be getting myself into regarding a system that is supported / supportable. As far as what to keep, I haven't the foggiest idea what is really in a profile. So having a Franken-profile doesn't seem like the best approach for Future Me... never mind how often I ignore that concern :).

A complication is that I find the structure of profiles to be an incomprehensible abyss. I'm sure some people understand how they work.
_________________
Quis separabit? Quo animo?

Anon-E-moose · Posted: Sat Apr 06, 2024 10:27 pm Post subject:

The profiles are indeed a little .. abstruse. The parent files are what's important.

Lets say your profile points to default/linux/amd64/17.1/desktop
in that directory, is an eapi file and a parent file.

pjp · Administrator Joined: 16 Apr 2002 Posts: 20067

I'll keep it in mind. Without having closely read the announcement, I'm leaning toward the binpkg method and a "manual" emptytree method. If I can deduce the "big" packages and exclude those, then maybe the emptytree option would work. Maybe mesa would be on the exclude list too? Other than gcc and llvm, nothing jumps out as obvious. Apparently I've set gdb to not use my tmpfs.

Then there's my chroot -> binpkg -> laptop situation.
_________________
Quis separabit? Quo animo?