From: Carlo Zancanaro <carlo@zancanaro.id.au>
To: Benjamin Slade <beoram@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: zig-build DNS issue (ghostty build)
Date: Fri, 03 Jan 2025 16:08:12 +1100 [thread overview]
Message-ID: <87cyh4bi2r.fsf@zancanaro.id.au> (raw)
In-Reply-To: <87wmfcppua.fsf_-_@gmail.com> (Benjamin Slade's message of "Thu, 02 Jan 2025 20:56:45 -0600")
Hi Benjamin,
On Thu, Jan 02 2025, Benjamin Slade wrote:
> I've got the start of a Guix package build for the new [Ghostty
> terminal emulator], but it gets stuck when the zig-build tries fetch
> some dependencies, with what I think is a DNS (!) issue:
Guix builds happen in a container which does not have access to the
network. Thus, you do have a DNS issues, but it's not one you can
resolve within a Guix package build.
Looking at the Ghostty documentation, their main build is with Nix,
which has the same network restriction, so that's a good sign that this
can be made to work. Looking at their PACKAGING.md[1], it says that the
only step which requires an internet connection is running this command:
--8<---------------cut here---------------start------------->8---
./nix/build-support/fetch-zig-cache.sh
--8<---------------cut here---------------end--------------->8---
Looking in that script[2], it basically just runs "zig build --fetch",
with some extra work to fetch some other dependencies. I'm not familiar
with Zig builds, but looking at build.zig.zon[3] it seems to list the
required dependencies.
To get a Guix package building you may need to package these
dependencies, and then provide them as inputs to your Ghostty package.
I'm not sure whether the Zig build system is set up to handle this
properly. I couldn't find any examples of Zig packages with Zig
dependencies, but I didn't try very hard.
I hope that helps,
Carlo
[1]: https://github.com/ghostty-org/ghostty/blob/e2f9eb6a6f4dc2108f91293938374c0ed314dcb8/PACKAGING.md
[2]: https://github.com/ghostty-org/ghostty/blob/e2f9eb6a6f4dc2108f91293938374c0ed314dcb8/nix/build-support/fetch-zig-cache.sh
[3]: https://github.com/ghostty-org/ghostty/blob/e2f9eb6a6f4dc2108f91293938374c0ed314dcb8/build.zig.zon
next prev parent reply other threads:[~2025-01-03 5:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 2:56 zig-build DNS issue (ghostty build) Benjamin Slade
2025-01-03 5:08 ` Carlo Zancanaro [this message]
2025-01-04 1:02 ` Benjamin Slade
2025-01-03 11:33 ` Murilo
2025-01-03 20:23 ` Benjamin Slade
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cyh4bi2r.fsf@zancanaro.id.au \
--to=carlo@zancanaro.id.au \
--cc=beoram@gmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).