From: Eli Schwartz <eschwartz@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Compile times on Raspberry Pi 5?
Date: Sun, 27 Apr 2025 01:07:24 -0400 [thread overview]
Message-ID: <0321cc41-be42-44df-84c7-d9c2cb7f93d9@gentoo.org> (raw)
In-Reply-To: <x26u77zlkldomr4mpoadxxydamya4puyyub22fot6xvcoxhrow@d5ulc6xhpn6d>
[-- Attachment #1.1: Type: text/plain, Size: 1217 bytes --]
On 4/27/25 12:38 AM, whiteman808 wrote:
> Hello Gentoo users
>
> Have you tried to install Gentoo on the Raspberry Pi 5? I want to
> buy one and set up budget home server on it.
>
> How much average time it will take before I'll have working stage3 with
> running nginx, gitea, docker etc.? Will it take days or can I finish
> setting up rpi server in one day?
>
> I mean running Gentoo arm64 from official hat providing nvme support,
> not microSD card.
>
> Will compile times be similar to achieved on my old Lenovo ThinkPad
> X220? If so, that would be acceptable for me.
>
> Thank you, whiteman808
You may optionally choose to use the official binhost, in which case you
will avoid quite a bit of compilation. For example, nginx and docker are
both available as binpackages (but not gitea, which is not even stable
for arm64).
https://wiki.gentoo.org/wiki/Gentoo_Binary_Host_Quickstart
As usual with binpackages, this fully respects your USE flags (but not
CFLAGS) and transparently falls back to compiling from source for all
packages:
- without binary availability, or
- for which you prefer a specific USE flag lacking in binary
availability
--
Eli Schwartz
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2025-04-27 5:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-27 4:38 [gentoo-user] Compile times on Raspberry Pi 5? whiteman808
2025-04-27 5:07 ` Eli Schwartz [this message]
2025-04-27 15:40 ` yahoo
2025-04-27 21:06 ` Nate Eldredge
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=0321cc41-be42-44df-84c7-d9c2cb7f93d9@gentoo.org \
--to=eschwartz@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