unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: Hilton Chain <hako@ultrarare.space>, 66723@debbugs.gnu.org
Cc: "Nguyễn Gia Phong" <mcsinyx@disroot.org>,
	"Ludovic Courtès" <ludo@gnu.org>
Subject: [bug#66723] [PATCH 0/3] gnu: zig-0.10: Inherit from zig-0.9.
Date: Thu, 23 Nov 2023 17:23:11 +0100	[thread overview]
Message-ID: <a435e3f1-fe7f-b5fe-f8e0-761724b34940@elenq.tech> (raw)
In-Reply-To: <87cyw0trxi.wl-hako@ultrarare.space>

Hi,

On 11/23/23 16:23, Hilton Chain wrote:
> Hi,
> 
> On Sun, 19 Nov 2023 19:35:13 +0800, Nguyễn Gia Phong wrote:
>>
>> Should we keep Zig 0.9?  All currently packaged Zig programs requires it
>> anymore AFAICT, and the language is immature enough I'd argue we should only
>> keep older versions when necessary.
>>
>> Your patchset adding LLVM 16 has been applied BTW, I can't wait for Zig 0.11!
> 
> 
> I didn't realise that Zig 0.11 includes a binary file when sending the cover
> letter.  So I haven't bootstrapped it yet, sorry that I didn't mention this
> earlier...
> 
> Though Zig 0.11 is not bootstrapped, here's a patch to use it at the moment:
> https://paste.sr.ht/~hako/c6fb3a872c1e91a09500bf1288e128215ca80d12
> 
> 
> I have no experience in both bootstrapping and Zig, so I don't know exactly what
> to do further.

We can talk about how to do it, I'm not sure about it yet.

> (Cc-ed Ekaitz since they are more familiar with the topic)

Thanks for keeping me on the loop. I missed this thread.

> For Zig I think the first step is to create a path from the last commit that has
> a stage1:
>      4e2a960b523070c7f8fddf0ea9b6e2a94e31dafe (std.fs: fix openDirAbsolute)
> to the addition of the binary file:
>      20d86d9c63476b6312b87dc5b0e4aa4822eb7717 (add zig1.wasm.zst)
> 
> But for now I'm not sure how.
> 
> 
> On Wed, 22 Nov 2023 20:12:43 +0800, Ludovic Courtès wrote:
>>
>> Hi Hilton,
>>
>> Hilton Chain <hako@ultrarare.space> skribis:
>>
>>> This series applies gexp to package arguments of zig@0.9 and zig@0.10, and
>>> makes the latter inherit from the former.
>>>
>>> I have already packaged zig@0.11, which depends on LLVM 16
>>> (https://issues.guix.gnu.org/66701), will send the patch soon.
>>>
>>> Hilton Chain (3):
>>>    gnu: zig-0.10: Use gexp.
>>>    gnu: zig-0.9: Use gexp.
>>>    gnu: zig-0.10: Inherit from zig-0.9.
>>
>> It’s been a while, and I think this patch series can go in.
>>
>> As Nguyễn Gia Phong, we should question whether to keep zig 0.9, but that can
>> come later.
> 
> 
> Thank you!  I'll push the series this weenkend.

My 2 cents here:

I made a very similar package to this one on my own. But the tests are 
failing for cross compilation targets. This is not cool. I think you 
just disabled those but we do have an issue reported at Zig 
(https://github.com/ziglang/zig/issues/18063) that is relevant.
I don't mind to leave this as you proposed at the moment, this issue 
will take long to fix, probably.

I just read the changes diagonally but I think my research leads to the 
same resulting package so this patch series look pretty ok to me.

We need to discuss that bootstrapping issue though.
Feel free to reach me in IRC and we can find a solution together, or we 
can continue the discussion here.

I tried to avoid the webassembly thingie using an older zig version 
without it and making the bootstrapping à la rust, but as zig changes 
fast using the previous version as a stage2 compiler simply doesn't 
work. We need to catch some commit in the middle and probably make 
incremental packages until we reach the current zig. Doesn't feel 
reasonable, so we may need to find other kind of solution.

As said, we need to discuss this.

Thanks for the patches and for keeping me on the loop.

Ekaitz




  reply	other threads:[~2023-11-23 16:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24  8:23 [bug#66723] [PATCH 0/3] gnu: zig-0.10: Inherit from zig-0.9 Hilton Chain via Guix-patches via
2023-10-24  8:34 ` [bug#66723] [PATCH 1/3] gnu: zig-0.10: Use gexp Hilton Chain via Guix-patches via
2023-10-24  8:34 ` [bug#66723] [PATCH 2/3] gnu: zig-0.9: " Hilton Chain via Guix-patches via
2023-10-24  8:34 ` [bug#66723] [PATCH 3/3] gnu: zig-0.10: Inherit from zig-0.9 Hilton Chain via Guix-patches via
2023-11-19 11:35 ` [bug#66723] [PATCH 0/3] " guix-patches--- via
2023-11-23 15:23   ` Hilton Chain via Guix-patches via
2023-11-23 16:23     ` Ekaitz Zarraga [this message]
2023-11-25 14:10     ` bug#66723: " Hilton Chain via Guix-patches via
2023-11-22 12:12 ` [bug#66723] " Ludovic Courtès

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=a435e3f1-fe7f-b5fe-f8e0-761724b34940@elenq.tech \
    --to=ekaitz@elenq.tech \
    --cc=66723@debbugs.gnu.org \
    --cc=hako@ultrarare.space \
    --cc=ludo@gnu.org \
    --cc=mcsinyx@disroot.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).