From: Rutherther <rutherther@ditigal.xyz>
To: Ethan Reece <guix@ethanreece.com>
Cc: help-guix@gnu.org
Subject: Re: Cannot build "guix" on aarch64
Date: Wed, 25 Dec 2024 09:28:14 +0100 [thread overview]
Message-ID: <87bjx0majl.fsf@ditigal.xyz> (raw)
In-Reply-To: <9da787df-6a02-4011-a5a2-87a032cbedb9@app.fastmail.com>
Hi Ethan,
Nice to hear you got it fixed after all!
>
> Hi Rutherther,
>
> I did some more tests and found out that the `guix` package compiles successfully if I make my /tmp directory use my root BTRFS partition instead of Tmpfs. Somebody on Github[1] thinks this has to do with the 16kb Tmpfs sector sizes that Asahi Linux uses due to having a 16k page size instead of 4k that x86 machines use and also filed a report on debbugs[2]. I'm not sure why Guix worked previously, but I also noticed while testing that I couldn't compile an old (August) version of the Guix repo either so I'm guessing that an Asahi Fedora update changed the /tmp configuration and that's when the issue started.
That is interesting, I don't know why sector size would matter, but I
suppose it could be plausible. Note that with guix it's usually not so
good to have /tmp as tmpfs in general. The thing is that guix builds
there, and some builds can take up a lot of space + they are building,
so even consume ram by running the processes. So it's quite easy to
get out of RAM unless you have a lot of RAM. But if you were able
to build previously and the size of your /tmp tmpfs did not change,
I suppose that was not the issue here.
Regrads,
Rutherther
prev parent reply other threads:[~2024-12-25 9:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 7:44 Cannot build "guix" on aarch64 Ethan Reece
2024-12-15 19:28 ` Rutherther
2024-12-15 23:06 ` Ethan Reece
2024-12-23 20:07 ` Ethan Reece
2024-12-25 8:28 ` Rutherther [this message]
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=87bjx0majl.fsf@ditigal.xyz \
--to=rutherther@ditigal.xyz \
--cc=guix@ethanreece.com \
--cc=help-guix@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.