[gentoo-amd64] Re: Switching form non-multilib to mulitilib profile?

[Duncan]

Jakob <jak.gentoo@××××××××××.com> posted
a23345650612221005y6c0cd6c9iebeebf15edfec863@××××××××××.com, excerpted
below, on  Fri, 22 Dec 2006 19:05:26 +0100:

> On 12/22/06, Boyd Stephen Smith Jr. <bss03@××××××××××.net> wrote:
>> On Friday 22 December 2006 01:06, Mike Doty <kingtaco@g.o> wrote
>> about 'Re: [gentoo-amd64] Switching form non-multilib to mulitilib
>> profile?':
>> Well, Mike's probably a better source than me, but I thought the multilib
>> <-> no-multilib switch could be done with a simple emerge -e world.
>>
> I think I just try that and if it doesn't work no problem because I
> have to reinstall anyway.

The problem is that after you've emerged glibc and gcc using the
non-multilib profile, you no longer have a 32-bit capable compiler and
libc as no-multilib only compiles the 64-bit side.  Without a 32-bit
compiler and glibc, you can't (easily) compile the 32-bit compiler and
glibc necessary for multilib.

Thus, one can go multilib -> no-multilb simply by switching profiles and
remerging at minimum the toolchain, but it's a one-way switch.  Once you
are 64-bit only, you don't have the 32-bit stuff necessary to bootstrap
/further/ 32-bit stuff.  You therefore can't (easily) go the other way,
no-multilib -> multilib.

There are of course a number of ways around the problem, but the easiest,
because it's documented, is to simply reinstall from stage-3 using the
multilb profile.  Anything else, you'd better know what you are doing
(which it's safe to say you don't if you are asking the question), as you
are on your own, at least in terms of official Gentoo/amd64 documentation.

However, most packages will be 64-bit only anyway, thus the same in both
cases (unless one requires a different version for some reason or other),
and of course any 32-bit binary packages (like the emul* packages) aren't
difficult to merge once on multilib, if needed.  Thus, the only ones you
really need to worry about are the toolchain, basically glibc, gcc,
binutils, and portage's sandbox (which has both 32-bit and 64-bit
libraries in multilib mode).

Thus, the quick method would be to quickpkg those packages (glibc, gcc,
binutils, sandbox) off of a stage-3, change the profile, and merge the
quickpkg-ed binpkgs over the 64-bit-only versions.  After that, it
/should/ be possible to remerge just those packages, instead of having to
remerge the entire system, to get full multilib.  (It's likely you have to
switch the profile and merge the four binpkgs in a specific order,
however, which I might not have correct, above, and it's possible there's
a multilib package or two I missed, but I don't think so.) If anything goes
wrong, as you said, you'd just have to do the reinstall that was the other
option anyway, so nothing lost.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@g.o mailing list