public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] CFLAGS Core2Duo
Date: Tue, 19 Dec 2006 19:41:49 -0600	[thread overview]
Message-ID: <200612191941.54957.bss03@volumehost.net> (raw)
In-Reply-To: <1166576188.31071.6.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 1781 bytes --]

On Tuesday 19 December 2006 18:56, "W.Kenworthy" <billk@iinet.net.au> wrote 
about 'Re: [gentoo-user] CFLAGS Core2Duo':
> Is it still the case thats its impossible to upgrade a 32bit gentoo on
> athlon64 to 64 bit - requires a full reinstall?

Reinstall is the only officially supported manner.

However, with a little bit of work, it *is* possible to upgrade.  The 50km 
view is:
1. Build cross toolchain -- portage may not make this easy
2. Use said toolchain to build 64-bit kernel with 32-bit support.
2a.If you need any out-of-tree modules before step 6, rebuild them with the 
cross compiler -- portage *will* *not* make this easy.
3. Reboot into new kernel.
4. Change CHOST in make.conf
5. Update toolchain configuration/symlinks to treat what was a cross 
toolchain as the native toolchain
6. Rebuild remaining out-of-tree modules.

At this point, only your kernel and modules are 64-bit, but each time your 
update/reinstall a package it will become 64-bit.  For best results, it'd 
probably a good time to rebuild the toolchain again.  (Right now, the 
tollchain is 32-bit code that produces 64-bit code.)

There's also some sticky issues with lib vs. lib32 vs. lib64 
directories/symlinks and your ldconfig and you may need a few runs of 
fix_libtool_files.sh and/or revdep-rebuild as required.

It's possible, but not really fun and very fragile, which is why there's no 
support for it.  If you want to try, I'm willing to help, but I can't 
guarantee anything, and many on the list will be unwilling to help.

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-12-20  1:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-19 19:18 [gentoo-user] CFLAGS Core2Duo Jakob
2006-12-19 19:36 ` Boyd Stephen Smith Jr.
2006-12-19 19:48   ` Jakob
2006-12-19 20:13     ` Boyd Stephen Smith Jr.
2006-12-19 20:46       ` Andrew Gaydenko
2006-12-19 22:38         ` Boyd Stephen Smith Jr.
2006-12-20  0:08           ` Jakob
2006-12-20  6:43           ` Andrew Gaydenko
2006-12-20 11:42             ` Bo Ørsted Andresen
2006-12-19 20:56       ` Jakob
2006-12-19 20:58         ` Jakob
2006-12-20  0:56           ` W.Kenworthy
2006-12-20  1:41             ` Boyd Stephen Smith Jr. [this message]
2006-12-20 15:09           ` A. Khattri
2006-12-19 22:23         ` Boyd Stephen Smith Jr.

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=200612191941.54957.bss03@volumehost.net \
    --to=bss03@volumehost.net \
    --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