Re: Bootstrapping Zig with no binary blobs: status update and call for packages.

Re: Bootstrapping Zig with no binary blobs: status update and call for packages.

[Ashvith Shetty]

Hi Hilton,

There's a lot of builds happening (perhaps related to the Zig 
sub-versions) when I try to build Zig 0.13 locally to test building a 
package of my choice. Is there a way to navigate this blocker?

Regards,
Ashvith

Bootstrapping Zig with no binary blobs: status update and call for packages.

[Hilton Chain]

Hello Guix!

After working on 'wip-zig-bootstrap' branch for the past month[1], I'm glad to
say it's ready for testing now!

+ Zig is bootstrapped to the current release, 0.13.0!

Greatly thanks to Motiejus!  I cannot find out the way without them finishing
the trickiest part.  They have also published a blog post[2].

You can now use Zig 0.13.0 and everything on wip-zig-bootstrap via
‘guix time-machine’, for example:
--8<---------------cut here---------------start------------->8---
guix time-machine \
        --no-channel-files \
        --branch=wip-zig-bootstrap \
        -- shell zig@0.13
--8<---------------cut here---------------end--------------->8---

Building 0.13 from the beginning of bootstrap chain takes around 5 hours on my
machine.  Efraim is building the branch on berlin so there should be some
substitutes on ci.guix.gnu.org, at least for sources.

Patches for adjusting linking behavior have been applied to all release versions
we currently have (0.9.1, 0.10.1, 0.11.0, 0.12.1, 0.13.0).  They should work
just fine without any extra workaround, please report to [1] if you encounter
any issue.

+ Cross build and Zig package manager support are available in zig-build-system.

zig-build-system now by default installs source under "/src" of package output.
Like in go-build-system, this can be disabled by setting #:install-source? to #f.

Other new arguments, #:skip-build? and #:zig-inputs, like the ones in
cargo-build-system, are available.  Note that packages and sources in
#:zig-inputs must have their output names starting with "zig-".

Example packages are available in (gnu packages zig-xyz) on wip-zig-bootstrap[3].

These new features need testing, please send your favorite packages to
guix-patches@gnu.org, targeting wip-zig-bootstrap and prefixed with "zig-team",
the more the better :)


Cheers,
Hilton
---
[1]: Bootstrapping Zig with no Binary Blobs
     https://issues.guix.gnu.org/74217

[2]: Zig Reproduced Without Binaries
     https://jakstys.lt/2024/zig-reproduced-without-binaries/

[3]: https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/zig-xyz.scm?h=wip-zig-bootstrap

Re: Bootstrapping Zig with no binary blobs: status update and call for packages.

[Hilton Chain]

Hi Ashvith,

On Mon, 02 Dec 2024 04:39:09 +0800,
Ashvith Shetty wrote:
>
> There's a lot of builds happening (perhaps related to the Zig sub-versions)
> when I try to build Zig 0.13 locally to test building a package of my
> choice. Is there a way to navigate this blocker?

I'm building them on my server so there're substitutes on [1], I didn't mention
it before because it requires extra authorization.

Thanks
---
[1]: https://substitute.boiledscript.com

Re: Bootstrapping Zig with no binary blobs: status update and call for packages.

[Efraim Flashner]

[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]

On Mon, Dec 02, 2024 at 07:19:11AM +0800, Hilton Chain wrote:
> Hi Ashvith,
> 
> On Mon, 02 Dec 2024 04:39:09 +0800,
> Ashvith Shetty wrote:
> >
> > There's a lot of builds happening (perhaps related to the Zig sub-versions)
> > when I try to build Zig 0.13 locally to test building a package of my
> > choice. Is there a way to navigate this blocker?
> 
> I'm building them on my server so there're substitutes on [1], I didn't mention
> it before because it requires extra authorization.
> 
> Thanks
> ---
> [1]: https://substitute.boiledscript.com

Also the substitutes on berlin (ci.guix.gnu.org) might need to be baked
before they're served.  So if it says there aren't substitutes it may be
worth waiting a few minutes and asking again to see if they just hadn't
been requested previously.

-- 
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 --]

Re: Bootstrapping Zig with no binary blobs: status update and call for packages.

[Ashvith Shetty]

[-- Attachment #1: Type: text/plain, Size: 857 bytes --]

Hi Hilton,

I left the build running overnight, and that did the job for me.

Bun is a little tricky to package, as it requires providing a modified
JavaScript core from oven-sh/WebKit <https://github.com/oven-sh/WebKit>,
and then there's a bunch of other dependencies that aren't clearly
specified. To be honest, I am not even sure which tag to start with, would
appreciate some guidance here.

So far, I've packaged waylock. Since I am on Xorg for the time-being, I
would really appreciate it if anyone using Wayland would test this
<https://codeberg.org/Ashvith/guix/src/branch/add-waylock> out - because
the PAM configuration
<https://codeberg.org/ifreund/waylock/src/branch/master/pam.d/waylock> may
have to be modified from system-auth to login - however, I could not get
swaylock working, which has "auth include login" by default.

Regards,
Ashvith

[-- Attachment #2: Type: text/html, Size: 1067 bytes --]

Re: Bootstrapping Zig with no binary blobs: status update and call for packages.

[Hilton Chain]

On Mon, 02 Dec 2024 19:30:38 +0800,
Ashvith Shetty wrote:
>
> [1  <text/plain; UTF-8 (7bit)>]
> I left the build running overnight, and that did the job for me.
>
> Bun is a little tricky to package, as it requires providing a modified
> JavaScript core from oven-sh/WebKit <https://github.com/oven-sh/WebKit>,
> and then there's a bunch of other dependencies that aren't clearly
> specified. To be honest, I am not even sure which tag to start with, would
> appreciate some guidance here.

Looks complex, and has bootstrappability issue it seems.

> So far, I've packaged waylock. Since I am on Xorg for the time-being, I
> would really appreciate it if anyone using Wayland would test this
> <https://codeberg.org/Ashvith/guix/src/branch/add-waylock> out - because
> the PAM configuration
> <https://codeberg.org/ifreund/waylock/src/branch/master/pam.d/waylock> may
> have to be modified from system-auth to login - however, I could not get
> swaylock working, which has "auth include login" by default.

Package works for me.  That file won't be used, screen-locker-service-type will
generate one instead.

Re: Bootstrapping Zig with no binary blobs: status update and call for packages.

[Hilton Chain]

On Tue, 03 Dec 2024 23:37:01 +0800,
Hilton Chain wrote:
>
> On Mon, 02 Dec 2024 19:30:38 +0800,
> Ashvith Shetty wrote:
> >
> > So far, I've packaged waylock. Since I am on Xorg for the time-being, I
> > would really appreciate it if anyone using Wayland would test this
> > <https://codeberg.org/Ashvith/guix/src/branch/add-waylock> out - because
> > the PAM configuration
> > <https://codeberg.org/ifreund/waylock/src/branch/master/pam.d/waylock> may
> > have to be modified from system-auth to login - however, I could not get
> > swaylock working, which has "auth include login" by default.
>
> Package works for me.  That file won't be used, screen-locker-service-type will
> generate one instead.

Applied your waylock package to wip-zig-bootstrap with some adjustments.

Re: Bootstrapping Zig with no binary blobs: status update and call for packages.

[Ludovic Courtès]

Hello Hilton,

Hilton Chain <hako@ultrarare.space> skribis:

> After working on 'wip-zig-bootstrap' branch for the past month[1], I'm glad to
> say it's ready for testing now!

This is quite an achievement, congrats!

Ludo’.

Re: Bootstrapping Zig with no binary blobs: status update and call for packages.

[Hilton Chain]

On Fri, 29 Nov 2024 22:39:10 +0800,
Hilton Chain wrote:
>
> Other new arguments, #:skip-build? and #:zig-inputs, like the ones in
> cargo-build-system, are available.  Note that packages and sources in
> #:zig-inputs must have their output names starting with "zig-".

Amend: #:zig-inputs will be removed in the end.  Now it's recommended to add Zig
dependencies to the standard inputs and propagated-inputs fields, and change
dependency names within package sources instead of embed the name mapping into
build system arguments.

A new procedure 'rename-zig-dependencies' is added for producing the needed
origin snippet.  Examples are available in zig-xyz.scm.