all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: 61036@debbugs.gnu.org
Cc: Efraim Flashner <efraim@flashner.co.il>
Subject: [bug#61036] [PATCH 0/3] Update zig to 0.10.1
Date: Tue, 24 Jan 2023 11:42:17 +0200	[thread overview]
Message-ID: <cover.1674553213.git.efraim@flashner.co.il> (raw)

After looking heavily through the sources I'm of the opinion that zig
0.10.1 doesn't use the new binary bootstrap that they've developed.

I'm unsure what to do with $output/bin/zig not finding ld-linux in its
RUNPATH, but it's the only thing that's left me unhappy.

I wasn't sure if we wanted to keep 0.9 around also, but I didn't want to
be responsible for updating zig-zls so I figured we'd keep it for now,
especially since they make a point of saying that the language isn't
finalized at its 1.0 release yet.


Efraim Flashner (2):
  gnu: zig: Update to 0.10.1.
  gnu: ncdu: Update to 2.2.2.

 gnu/packages/ncdu.scm    |   6 +--
 gnu/packages/zig-xyz.scm |   2 +-
 gnu/packages/zig.scm     | 100 +++++++++++++++++++++++++++++++--------
 3 files changed, 85 insertions(+), 23 deletions(-)


base-commit: 5965d74c8ce53d0861af9ad3744844ac925c4a12
-- 
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





             reply	other threads:[~2023-01-24  9:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24  9:42 Efraim Flashner [this message]
2023-01-24  9:46 ` [bug#61036] [PATCH 1/2] gnu: zig: Update to 0.10.1 Efraim Flashner
2023-06-06  5:57   ` bug#61036: " Efraim Flashner
2023-01-24  9:46 ` [bug#61036] [PATCH 2/2] gnu: ncdu: Update to 2.2.2 Efraim Flashner

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=cover.1674553213.git.efraim@flashner.co.il \
    --to=efraim@flashner.co.il \
    --cc=61036@debbugs.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.