From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: update fails, but I don't see why
Date: Mon, 14 Dec 2020 16:32:18 +0000 [thread overview]
Message-ID: <2786810.VdNmn5OnKV@lenovo.localdomain> (raw)
In-Reply-To: <585209e9-0859-579a-27d9-ba27df7b1763@web.de>
[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]
On Monday, 14 December 2020 12:55:33 GMT n952162 wrote:
> On 12/14/20 11:17 AM, Wols Lists wrote:
> > On 14/12/20 08:51, Dale wrote:
> >> If you are able, maybe you can compile the bigger packages on a faster
> >> system? If it is a option, it may help.
> >
> > If I have multiple similar machines, I create a shared a shared local
> > repository. Then I run emerge with the settings (can't remember what
> > they are) "use binary if it's there, create binary".
> >
> > That way, especially the big ones, only get built on one machine.
> >
> > Cheers,
> > Wol
>
> Oh man! That would be wonderful. How similar do they need to be? All
> my x86 machines are currently AMD, I think, but probably from different
> generations.
It depends on the different instruction sets between the CPUs. You could try
compiling one package as a test with the existing $COMMON_FLAGS on the fast
host and emerge '--buildpkg y', or '--buildpkgonly', then emerge it as a
binary on the slow host with '--usepkgonly y'.
If the binary package does not emerge/run on the slow host, then you can try
again, but use COMMON_FLAGS="-march" instead of "-march=native" to compile it
on the fast host. The same binary package could then be installed on all slow
hosts.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-12-14 16:32 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 20:33 [gentoo-user] update fails, but I don't see why n952162
2020-12-03 20:48 ` antlists
2020-12-03 21:04 ` Matt Connell (Gmail)
2020-12-03 21:06 ` tastytea
2020-12-03 21:11 ` Adam Carter
2020-12-04 8:13 ` n952162
2020-12-07 12:31 ` John Covici
2020-12-07 12:59 ` Arve Barsnes
2020-12-07 13:07 ` John Covici
2020-12-03 22:04 ` Victor Ivanov
2020-12-03 23:08 ` Neil Bothwick
2020-12-04 8:41 ` n952162
2020-12-04 8:53 ` Arve Barsnes
2020-12-04 9:10 ` antlists
2020-12-04 9:35 ` n952162
2020-12-04 10:07 ` Arve Barsnes
2020-12-04 19:52 ` n952162
2020-12-04 20:00 ` n952162
2020-12-04 20:25 ` n952162
2020-12-04 21:49 ` Arve Barsnes
2020-12-04 22:13 ` n952162
2020-12-04 22:19 ` n952162
2020-12-04 22:40 ` Jack
2020-12-05 8:48 ` n952162
2020-12-06 12:32 ` Neil Bothwick
2020-12-05 9:06 ` n952162
2020-12-05 9:41 ` n952162
2020-12-05 10:13 ` Dale
2020-12-05 11:06 ` n952162
2020-12-05 13:42 ` Victor Ivanov
2020-12-06 6:46 ` Dale
2020-12-12 22:08 ` n952162
2020-12-12 22:35 ` Neil Bothwick
2020-12-13 0:09 ` Dan Egli
2020-12-13 19:31 ` n952162
2020-12-13 19:48 ` n952162
2020-12-13 20:49 ` Arve Barsnes
2020-12-13 19:56 ` cal
[not found] ` <32af647f-a0e1-77e7-ff0f-4a5495e45f6b@web.de>
2020-12-13 8:18 ` Neil Bothwick
2020-12-13 8:57 ` n952162
2020-12-13 9:55 ` Michael
2020-12-13 21:10 ` n952162
2020-12-13 21:51 ` Dale
2020-12-14 0:04 ` Michael
2020-12-14 6:58 ` n952162
2020-12-13 10:07 ` n952162
2020-12-13 10:09 ` n952162
2020-12-13 22:10 ` Walter Dnes
2020-12-20 16:49 ` Peter Humphrey
2020-12-13 18:58 ` n952162
2020-12-13 19:48 ` Mark Knecht
2020-12-13 20:06 ` Dale
2020-12-13 21:02 ` n952162
2020-12-13 21:14 ` n952162
2020-12-13 21:40 ` Dale
2020-12-14 6:38 ` n952162
2020-12-13 21:31 ` Dale
2020-12-14 3:46 ` [gentoo-user] " Grant Edwards
2020-12-14 6:47 ` [gentoo-user] " n952162
2020-12-13 21:39 ` antlists
2020-12-14 6:50 ` n952162
2020-12-13 23:41 ` Neil Bothwick
2020-12-13 23:35 ` Neil Bothwick
2020-12-14 3:54 ` [gentoo-user] " Grant Edwards
2020-12-14 6:54 ` n952162
2020-12-14 8:43 ` Neil Bothwick
2020-12-14 8:51 ` Dale
2020-12-14 10:17 ` Wols Lists
2020-12-14 12:55 ` n952162
2020-12-14 16:32 ` Michael [this message]
2020-12-14 23:38 ` antlists
2020-12-14 23:47 ` Grant Edwards
2020-12-13 8:49 ` [gentoo-user] " n952162
2020-12-04 22:46 ` Neil Bothwick
2020-12-05 8:54 ` n952162
2020-12-06 12:27 ` Neil Bothwick
2020-12-04 10:08 ` Adam Carter
2020-12-29 22:07 ` [gentoo-user] update fails, but I don't see why [PROGRESS] n952162
2020-12-29 22:16 ` n952162
2020-12-29 22:32 ` Dale
2020-12-29 22:55 ` Neil Bothwick
2020-12-30 0:05 ` Michael
2020-12-30 0:21 ` Dale
2020-12-30 7:26 ` n952162
2020-12-30 7:22 ` n952162
2020-12-30 9:53 ` Michael
2020-12-30 7:42 ` n952162
2020-12-30 8:35 ` Arve Barsnes
2020-12-30 11:56 ` n952162
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=2786810.VdNmn5OnKV@lenovo.localdomain \
--to=confabulate@kintzios.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