From: whiteman808 <whiteman808@paraboletancza.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Changing CPU and motherboard
Date: Sat, 28 Jun 2025 21:10:58 +0200 [thread overview]
Message-ID: <cecy3a2wpd5qby5qiewnjqlk74d42mzswacdc5xal6u7w4ol6u@5vicrl5f66qo> (raw)
In-Reply-To: <56a33a7d-cad0-42a4-90f6-19477e567311@gentoo.org> <56a33a7d-cad0-42a4-90f6-19477e567311@gentoo.org>
On 28 Jun 2025, 10:33:24, Jay Faulkner wrote:
> On 6/28/2025 9:38 AM, whiteman808 wrote:
> > Is it necessary to reinstall Gentoo if I change CPU or motherboard? If
> > not, what steps should be done on the existing Gentoo installation? Do I
> > need to do these operations from chroot?
>
> I'm assuming this is amd64->amd64.
>
> So the main thing to worry about is CPU compatibility, and your CFLAGS. If
> you're using -march=native, there's a chance your system won't work as
> compiled. This isn't always true, but these days it's no longer a guarantee
> that a newer CPU will have all the features of the old.
>
>
> What I usually do in this case is:
>
> - set -march=x86-64-v3 (or whatever lowest-common-denominator CPU arch
> generic target works) --
> https://wiki.gentoo.org/wiki/Safe_CFLAGS#Generic_psABI_levels can help with
> this. - Ensure my system is fully updated, and `emerge --depclean`'d. -
> emerge -e @world # this will rebuild your entire system.
>
>
> You can *significantly* reduce the pain of this by using the binary package
> host.
>
>
> -JayF
Should I execute `emerge -e @world` inside chroot on some livecd?
next prev parent reply other threads:[~2025-06-28 19:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-28 16:38 [gentoo-user] Changing CPU and motherboard whiteman808
2025-06-28 17:33 ` Jay Faulkner
2025-06-28 17:49 ` Michael
2025-06-28 19:10 ` whiteman808 [this message]
2025-06-28 19:57 ` Jay Faulkner
2025-06-28 19:32 ` Dale
2025-06-28 19:44 ` whiteman808
2025-06-28 20:10 ` Dale
2025-06-28 20:15 ` Michael
2025-06-29 0:33 ` Dale
2025-06-28 23:04 ` whiteman808
2025-06-29 0:39 ` Dale
2025-06-29 2:23 ` Frank Steinmetzger
2025-06-29 1:17 ` Jay Faulkner
2025-06-29 17:51 ` [gentoo-user] " Grant Edwards
2025-06-29 2:19 ` [gentoo-user] " Frank Steinmetzger
2025-06-29 7:44 ` Michael
2025-06-29 17:55 ` [gentoo-user] " Grant Edwards
2025-06-29 17:54 ` Grant Edwards
2025-07-01 16:22 ` [gentoo-user] " Steven Lembark
2025-07-01 22:58 ` Jay Faulkner
2025-06-29 17:48 ` [gentoo-user] " Grant Edwards
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=cecy3a2wpd5qby5qiewnjqlk74d42mzswacdc5xal6u7w4ol6u@5vicrl5f66qo \
--to=whiteman808@paraboletancza.org \
--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