From: Efraim Flashner <efraim@flashner.co.il>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: Andreas Enge <andreas@enge.fr>,
pukkamustard <pukkamustard@posteo.net>,
guix-devel@gnu.org
Subject: Re: Zig on core-updates
Date: Mon, 17 Apr 2023 16:01:21 +0300 [thread overview]
Message-ID: <ZD1DIeEyLscfzKA3@3900XT> (raw)
In-Reply-To: <20230411051147.nlhz7nvhlhh3fvzc@thebird.nl>
[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]
On Tue, Apr 11, 2023 at 07:11:47AM +0200, Pjotr Prins wrote:
>
> On Mon, Apr 10, 2023 at 05:56:52PM +0200, Andreas Enge wrote:
> > Am Fri, Mar 17, 2023 at 09:33:31AM +0000 schrieb pukkamustard:
> > > A hunch: This might have something to do with Zig not properly
> > > supporting glibc 2.35: https://github.com/ziglang/zig/issues/12808
> >
> > Thanks, this looks like a good explanation of the problem, but I do not
> > quite see what could be a solution... I see a string of issues of the form
> > "add support for targeting glibc ..."
> > https://github.com/ziglang/zig/issues/12808
> > https://github.com/ziglang/zig/issues/12809
> > https://github.com/ziglang/zig/issues/14798
> > but all of them are open.
> >
> > We may have to do without zig in the foreseeable future...
> >
>
> They just added a tag for the next release. We can wait.
We may have to backport whatever fix they do, it looks like 0.11 is
going to use their new bootstrap chain, with a pre-compiled zig wasm
binary.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-04-17 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 13:44 Zig on core-updates Andreas Enge
2023-03-17 9:33 ` pukkamustard
2023-04-10 15:56 ` Andreas Enge
2023-04-11 5:11 ` Pjotr Prins
2023-04-17 13:01 ` Efraim Flashner [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=ZD1DIeEyLscfzKA3@3900XT \
--to=efraim@flashner.co.il \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
--cc=pukkamustard@posteo.net \
/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.