public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matt Jolly <kangie@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Migrating existing Gentoo to binpkg
Date: Sat, 16 Nov 2024 00:15:22 +1000	[thread overview]
Message-ID: <c41ca6b3-91d8-4c18-a5eb-d4e0b7dbce4e@gentoo.org> (raw)
In-Reply-To: <173167455567.7.12220560602579978916.495919527@simplelogin.com>

Hi,

> Since I'm planning to use binary packages from x86-64-v3, I presume this 
> should be changed to:
> 
>      COMMON_FLAGS="-march=x86-64-v3 -O2 -pipe"
> 
> or, perhaps:
> 
>      COMMON_FLAGS="-march=x86-64-v3 -mtune=znver4 -O2 -pipe" ?

You want to match the binhost flags:

https://wiki.gentoo.org/wiki/Gentoo_Binary_Host_Quickstart#x86-64-v3_variant


> I also have a hefty $CPU_FLA
> GS_X86 (also added to $USE) from "cpuid2cpuflags" but am not worried 
> about this as packages that don't fit will simply be built from source 
> as usual.

You could also match with the flags the binhost has if you want to avoid
compilation altogether. See above.

> 1) What would be the preferred CFLAGS configuration

See above.

> 2) To reinstall the current source based packages with their binary 
> equivalent, "--rebuilt-binaries" sufficient or should I just go for "-- 
> emptytree @world"?
> 

If you're currently using x86-64-v4 there's no benefit to replacing the
existing packages. Just let them age out and be replaced over time as
as new versions are released.

Cheers,

Matt


  parent reply	other threads:[~2024-11-15 14:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-15 12:42 [gentoo-user] Migrating existing Gentoo to binpkg byte.size226
2024-11-15 14:05 ` Jacques Montier
2024-11-15 14:15 ` Matt Jolly [this message]
2024-11-15 14:52   ` byte.size226
2024-11-15 15:41     ` Eli Schwartz
2024-11-17 14:44       ` byte.size226
2024-11-18  9:21         ` Dr Rainer Woitok
2024-11-19 12:06           ` byte.size226
2024-11-15 15:36 ` Eli Schwartz

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=c41ca6b3-91d8-4c18-a5eb-d4e0b7dbce4e@gentoo.org \
    --to=kangie@gentoo.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