From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Moving from no-multilib to (true) multilib
Date: Mon, 30 Mar 2015 10:45:43 +0000 (UTC) [thread overview]
Message-ID: <pan.2015.03.30.10.45.43@googlemail.com> (raw)
In-Reply-To: 201503301120.39056.michaelkintzios@gmail.com
On Mon, 30 Mar 2015 11:20:23 +0100, Mick wrote:
> Given that the emul-linux-x86 package sets are now deprecated and we can now
> with USE="abi_x86_32" emerge our own 32bit libraries where needed, is it now
> easier to move from a no-multilib to a multilib environment, or will it still
> require a complete reinstall?
My understanding is that this has not changed, i.e. the move from prebuilt
emul-linux package to abi_x86_32 only applies to existing multilib systems.
Moving from "plain" aka non-multilib to multilib is still more or less
unsupported/impossible and requires a reinstall.
-h
next prev parent reply other threads:[~2015-03-30 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 10:20 [gentoo-user] Moving from no-multilib to (true) multilib Mick
2015-03-30 10:45 ` Holger Hoffstätte [this message]
2015-04-01 0:26 ` [gentoo-user] " NP-Hardass
2015-03-31 10:48 ` [gentoo-user] " Bruce Hill
2015-03-31 10:51 ` Alan McKinnon
2015-04-04 14:08 ` Bruce Hill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pan.2015.03.30.10.45.43@googlemail.com \
--to=holger.hoffstaette@googlemail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox