Build Desktop with no-multilib?

[cctsurf]

I have had a lot of suggested use: abi_x86_32 recently...
I was wondering why we are still running multilib systems. I know there is a lot of 32bit inertia here, but I was wondering if I could build a new install for my desktop that entirely avoided the 32bit binaries? (I use kde/plasma) Are there still lots of blockers for that idea? I suppose the only way to find out would be to try it in a VM or chroot...
Any Thoughts?
Thanks!

[Hu]

Multilib persists because switching from no-multilib to multilib is hard and officially unsupported, so anyone who expects to ever need multilib needs to start with it and stay with it. However, on a typical system that does not really need multilib, very few things will be built with it, and you should never get warnings about needing to adjust the abi_x86_32 settings.

The most common offender now is Windows games (including those sold through Steam to run on Linux through a Wine wrapper). Running a 32-bit Windows game requires a 32-bit Wine, which means multilib, or an x86 chroot. I think almost everything for which source is available, and for which anyone cares, has been ported to 64-bit by now.

[cctsurf]

That sounds REALLY encouraging.

I'm not running anything wine/Steam any more.

I think I'll see if I can build it in a chroot and how well it builds, then think about moving my system.
Thanks!

[NeddySeagoon]

cctsurf,

I've been no-multilib since Apr 2009 but I not a gamer.
_________________
Regards,

NeddySeagoon

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

[cctsurf]

As I think about this, is there a easy way to compare the use flags, etc. that are set by the different profiles? I'm guessing that I'm going to have to add the plasma subset to my make.conf file.

[NeddySeagoon]

cctsurf,

Choose a random profile.
Run

[pietinger]

[cctsurf]

[Hu]

That is comparatively easy. The switch from multilib->no-multilib is dropping the 32-bit pieces. The reverse is building those pieces, but you need them before you can build them, which is why enabling multilib is hard.

[stefan11111]

[stefan11111]

[asturm]

Dont.

[Zucca]

cctsurf,

There's very little risk going with no-multilib. Unless you specifically use Steam.

[Anon-E-moose]

If you leave the profile multilib, you can always set MULTILIB_ABI to just build 64bit stuff.

It leaves you with a minimal multilib system (basically glibc and gcc 32 bit stuff ... IIRC)
_________________
UM780, 6.12 zen kernel, gcc 13, openrc, wayland

[cctsurf]

Went to no-multilib, kinda wish I had seen some of the notes about keeping multilib, but with a minimum multilib, but I had already begun the recompile...

One problem I am running into:
On one system (I moved 2 to no-multilib), I am getting suggested rebuilds for a number of packages @preserved-rebuild stuff, but when I run emerge @preserved-rebuild, it doesn't rebuild anything.
I thought, "since I just made a fairly major move, maybe I should rebuild my entire system and that will get rid of it... nope. Still have the suggestion and no action when I attempt to rebuild.
Any Suggestions?

[pietinger]

[cctsurf]

So far, I'm failing at getting them to work. I attempted to follow the "sledgehammer" suggestion after trying the other previous options (it seems that that version of pango is no longer in the tree)... Still no dice.

[logrusx]

[cctsurf]

I went nuclear (or rather sledgehammer) because the earlier options in the above way (https://wiki.gentoo.org/wiki/User:Sam/Portage_help/Circular_dependencies) of resolving the circular dependency didn't solve the situation.
I couldn't do:

[logrusx]

[krumpf]

[logrusx]