On Sunday, April 10, 2016 08:09:28 AM Mick wrote:
> On Saturday 09 Apr 2016 23:08:13 Neil Bothwick wrote:
> > On Sat, 09 Apr 2016 22:41:01 +0100, Mick wrote:
> > > > I'd use the KDE profile. The packages you install are still the ones
> > > > you want but the profile means the USE flags are already as you need,
> > > > and you can always tweak any you want different anyway.
> > > 
> > > Reading eselect news I thought that the KDE profile and kde USE flag is
> > > due to be withdrawn with Plasma 5 going stable, did I get this wrong?
> > 
> > Sorry, I meant the plasma profile.
> 
> I just noticed, one box is set at:
> 
> [11]  default/linux/amd64/13.0/no-multilib *
> 
> Is this a reinstall exercise?

Usually yes, but there is a work-around:

Create a temporary chroot with a non-no-multilib installation.
Use that to create binary packages. 
Then change the profile of the main installation to a non-no-multilib profile
Using the packages created in the chroot, do an "emerge -e @world"

That worked for me. (Found this in a blogposting somewhere)

--
Joost