On Wednesday 27 May 2015 21:09:27 Neil Bothwick wrote: > On Wed, 27 May 2015 18:38:08 +0000 (UTC), James wrote: > > Eselect news list 2015-3-28 lists "True multilib support on amd64" > > > > For me, I run a simple profile: [1] default/linux/amd64/13.0 * > > > > Because I run lxde and have experimented with several other minimalistic > > desktops, including lxqt. Currently, I run lxde. If I emerge with the > > --deep option, I get so much breakage that 3000 lines of scrollback is > > not enough to get to the head of the problem. Many errors contain the > > common string "abi_x86_32" which is central to the aforementioned news > > item. I have read this news item many times, tried many ideas, and > > still have this phantom problem. I can delete some packages had at > > the update, hours to days, get it cleaned up to where -D works and a > > couple of emerge --syncs later the problem reappears. Global update > > without (-D) --deep are just fine. > > > > > > I have no idea if this "phantom issue" relates to yours or not. I have > > hesitated to post about it, because in a decade of gentoo usage (and > > there have been some ruff patches to say the least) I have never > > experienced a transient recurring problem like this. I think I need a > > much longer version of that news item and some cook_book syntax to > > fixing these (phantom) multilb issues on my amd64 systems that I am > > experiencing. > > > > Some simple questions:: > > > > 1. How do you test if indeed a system is multilib? > > It is, as you are not using a no-multilib profile. > > > 2. Can a system be change, readily, from multilib to not and then back? > > No. > > > 3. Is a more specific profile needed for one where you intend to > > run only a minimalist (lxqt) desktop (than what I listed above)? > > No, that is a fairly basic profile. > > > Comments and guidance are warmly appreciated. > > Peter I'm not trying to hijack your thread, but enquire as to > > commonality. > > Your problem is different but has been covered in previous threads, as > well as the news item. You could add ABI_X86="32 64" to make.conf, but > that won't fit in with your desire for minimalism. So you need to run > emerge with --autounmask-write then run etc-update or equivalent to apply > the changes to package.use.
Only to add that maintainers are regularly updating packages and this is why you may find that suddenly new packages require USE="abi_x86_32", when a week ago they didn't. It is worth noting that one multilib box of mine has not asked me (yet) to set USE="abi_x86_32" on any of its packages, while my laptop is regularly prompting me to do so. I have concluded that the former has no packages which are using 32bit code, while the latter does (I know that at least Skype is a culprit). So in extremis you could I guess purge any 32bit coded packages from your PC and the "abi_x86_32" prompts should leave you alone. I shouldn't forget to add your usual disclaimer: "YMMV" :-) -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
