Re: node-team / bootstrapping node packages

A little addition : tree-sitter-build-system supports cross-compilation, but node-build-system doesn't seem to support it ; it can probably be a useful goal to plan this. Nicolas On 2025-02-13 14:53, Jelle Licht wrote: > > A nonexhaustive list of things that could already be rolled into the no

Re: node-team / bootstrapping node packages

On 2025-02-13 14:53, Jelle Licht wrote: > - helper methods to package 'simple' packages: > https://issues.guix.gnu.org/68941 If you happen to take a look at this one, could you only care/merge the helper methods and not the packages ? I would like to move them to a node-bootstrap.scm module. --

Re: node-team / bootstrapping node packages

On 2025-02-13 14:53, Jelle Licht wrote: > Hi Nicolas, > > Nicolas Graves writes: > >> Hi guix, >> >> I was wondering if a node-team would be useful to make the work towards >> making a few applications available in Guix. > > Agreed! I've slightly broadened the scope to JavaScript packages in > ge

Re: node-team / bootstrapping node packages

Hello Jelle and Nicolas, Am Thu, Feb 13, 2025 at 02:53:28PM +0100 schrieb Jelle Licht: > Agreed! I've slightly broadened the scope to JavaScript packages in > general for new team at https://issues.guix.gnu.org/76268. this is a very welcome initiative! I think you can simply go ahead, Jelle, and

Re: node-team / bootstrapping node packages

Hi Nicolas, Nicolas Graves writes: > Hi guix, > > I was wondering if a node-team would be useful to make the work towards > making a few applications available in Guix. Agreed! I've slightly broadened the scope to JavaScript packages in general for new team at https://issues.guix.gnu.org/76268.

node-team / bootstrapping node packages

Hi guix, I was wondering if a node-team would be useful to make the work towards making a few applications available in Guix. It's been quite some time that 68941 is ready but forgotten. Based on this patch series, I'm now able to build a node-tape-bootstrap with minimal missing dependencies to

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

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 re

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

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

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

On Mon, 02 Dec 2024 19:30:38 +0800, Ashvith Shetty wrote: > > [1 ] > 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 , > and then the

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

Hello Hilton, Hilton Chain 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.

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 , and then there's a bunch of other dependencies that aren't clearly specified.

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

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

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

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

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

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.

u.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-binari

Re: Guix Social today - Bootstrapping RISC-V talk by Ekaitz

slides they're available here: https://ekaitz.elenq.tech/bootstrapGcc16.html Enjoy it! Futurile / Steve On 17 Sep, Steve George wrote: > Hi all, > > The next Guix Social is today, Tuesday, with a talk by Ekaitz Zarraga on > bootstrapping RISC-V. Times: > > 17:00 UTC, 18:00

Guix Social today - Bootstrapping RISC-V talk by Ekaitz

Hi all, The next Guix Social is today, Tuesday, with a talk by Ekaitz Zarraga on bootstrapping RISC-V. Times: 17:00 UTC, 18:00 BST (London), 19:00 CEST (Paris), 13:00 EDT (New York) Link to join: https://meet.jit.si/london-guix-meetup The bootstrapping problem is that many OS's

Re: Bootstrapping path discovered for RISC-V 64bit

On Wed, Jul 03, 2024 at 05:16:55PM +0200, Ekaitz Zarraga wrote: > Hi, > > Thanks to NlNet we have found a bootstrapping path for RISC-V 64 and we > created an alternative `commencement.scm` draft that builds from source up > to a GCC-9. > > At the moment, that GCC-9 does no

Bootstrapping path discovered for RISC-V 64bit

Hi, Thanks to NlNet we have found a bootstrapping path for RISC-V 64 and we created an alternative `commencement.scm` draft that builds from source up to a GCC-9. At the moment, that GCC-9 does not provide C++ support in my Guix packages. I tried to add it but I had issues. We made it work

Re: Guidelines for bootstrapping with lots of inputs

On 2024-02-20 15:11, Adam Faiz wrote: >> WDYT? Are there guidelines somewhere about how to do proper bootstrapping in >> these cases where hundreds of packages are involved? > > Not really, but your idea to rewrite inputs for the bootstrapping process > does simplify thi

Re: Guidelines for bootstrapping with lots of inputs

>How is typescript bootstrapped? Even though you'll have to repeat the trial >and error process again, I think using sucrase is easier for bootstrapping >typescript: https://lists.gnu.org/archive/html/guix-devel/2024-02/msg00122.html Nevermind, it's already bootstrapped with esbuild in guixrus.

Re: Guidelines for bootstrapping with lots of inputs

> WDYT? Are there guidelines somewhere about how to do proper bootstrapping in > these cases where hundreds of packages are involved? Not really, but your idea to rewrite inputs for the bootstrapping process does simplify things a lot. How is typescript bootstrapped? Even though you'

Guidelines for bootstrapping with lots of inputs

d to an approach where we explicitely define ...-bootstrap packages : - way less code - way more clarity about how the package is actually being bootstrapped. - we don't have to define packages twice, and that matters for PHP/Rust/JS where we have hundreds of packages for bootstrapping basic test nati

Re: GHC 8.6.5 build failure (bootstrapping)

Hi Lars-Dominik, On Sun, May 21, 2023 at 11:11 PM Lars-Dominik Braun wrote: > > could you share your changes? Here is my patch but the change was experimental and upon reflection makes little sense. I meant to allow 'env -S' to be used in hashbangs. Maybe my changes caused the build to fail. In

Re: GHC 8.6.5 build failure (bootstrapping)

Hi, > Everything looks great, except that GHC failed to build from source > locally. (I know GHC bootstraps separately.) I don't think my code > caused the failure, but it's possible. Looks like it failed in the > tests. could you share your changes? The logs are rather unhelpful. Cheers, Lars

GHC 8.6.5 build failure (bootstrapping)

Hi, While dreaming up potential improvements to 'patch-shebangs, I got to see our new full-source bootstrapping [1] and more. Congratulations! Everything looks great, except that GHC failed to build from source locally. (I know GHC bootstraps separately.) I don't think my code caused t

Re: Compiler bootstrapping requirements

Robby Zambito writes: > Hi, > > I remember seeing some details about certain compilers not being > allowed in Guix due to having an inadequate bootstrapping process, but > I can't seem to find it right now. I'm looking to write a package for > the Cyclone Scheme[1]

Compiler bootstrapping requirements

Hi, I remember seeing some details about certain compilers not being allowed in Guix due to having an inadequate bootstrapping process, but I can't seem to find it right now. I'm looking to write a package for the Cyclone Scheme[1] implementation. The compiler requires a copy of itsel

Re: [bootstrappable] Re: Mes Bootstrapping demonstration

Hi Aret, > If you don't want to use Guix, you may have a look at the live bootstrap > project > >https://github.com/fosslinux/live-bootstrap You might want to take a look at the following files: https://github.com/fosslinux/live-bootstrap/blob/master/sysa/run.kaem https://github.com/fosslin

Re: Mes Bootstrapping demonstration

Aret San writes: Hello Aret/John, > I heard that from GNU Mes 0.24 it's capable of being bootstrapped with > M2-Planet. Yes, see the core-updates branch. > But when I was trying to do that it ended up in some errors > in scm files `something related to (export)`. Sounds like a Nyacc problem.

Mes Bootstrapping demonstration

Hi, I heard that from GNU Mes 0.24 it's capable of being bootstrapped with M2-Planet. But when I was trying to do that it ended up in some errors in scm files `something related to (export)`. I also tried this in a busybox docker image where there's no gcc (not even guile), The M2-Planet and mescc

Re: bootstrapping scenario for a package

and did not find the > source of this minimal compiler--so it is a black box in a way. > > In free software it is ideal to build everything from source. I > wonder how is such a package handled in Guix? What is the strategy > for bootstrapping? Thanks In several important cases (

bootstrapping scenario for a package

compiler--so it is a black box in a way. In free software it is ideal to build everything from source. I wonder how is such a package handled in Guix? What is the strategy for bootstrapping? Thanks (msg sent to help-guix first but this list may be more appropriate)

Re: Crystal Bootstrapping Journey

tes, questions, and a list of dependencies regarding > what is needed to finish a properly bootstraped crystal package: > > https://github.com/ryanprior/guix-packages/blob/master/testing/crystal.org > > We are trying to recreate this bootstrapping process: > > https://github.com/cryst

Crystal Bootstrapping Journey

https://github.com/ryanprior/guix-packages/blob/master/testing/crystal.org We are trying to recreate this bootstrapping process: https://github.com/crystal-lang/bootstrap-script There are 160 stages! A few questions extracted from the notes follow: Is it preferable to have 160 bootstrap pac

Re: [TALK PROPOSAL] Bootstrapping the Java Ecosystem

Am 27.10.20 um 18:30 schrieb Julien Lepiller: > I'd like to talk about the Maven bootstrap and the Maven Build System. +1 -- Regards Hartmut Goebel | Hartmut Goebel | h.goe...@crazy-compilers.com | | www.crazy-compilers.com | compilers which you thought are impossible |

[TALK PROPOSAL] Bootstrapping the Java Ecosystem

Hi Guix! So, I guess we need to start collecting talk proposals for the online Guix Day in November. Here's mine :) I'd like to talk about the Maven bootstrap and the Maven Build System. Ensuring that software is built entirely from source is an essential practice to ensure user Freedom, as well

Re: Problem bootstrapping Guix - "make update-guix-package" result: no code for module (gcrypt hash)

Hi Danny, Danny Milosavljevic skribis: > I'm doing a project for Heads where we are trying to switch over their build > system to something that makes their builds more reproducible (for example > Guix). > > They are using github and gitlab test runners for a lot of things, so one of > the ways

Re: Problem bootstrapping Guix - "make update-guix-package" result: no code for module (gcrypt hash)

Hi Ludo, On Mon, 05 Oct 2020 14:20:08 +0200 Ludovic Courtès wrote: > Danny Milosavljevic skribis: > > > I'm trying to bootstrap current Guix (master) from Guix past (1.1.0 binary > > tarball). > > > > The goal is: I want to have only guix-the-package-manager at a specific guix > > commit (!) a

Re: Problem bootstrapping Guix - "make update-guix-package" result: no code for module (gcrypt hash)

Hi, Danny Milosavljevic skribis: > I'm trying to bootstrap current Guix (master) from Guix past (1.1.0 binary > tarball). > > The goal is: I want to have only guix-the-package-manager at a specific guix > commit (!) available inside a Docker image. Why build Guix from source? I guess it’s enou

Problem bootstrapping Guix - "make update-guix-package" result: no code for module (gcrypt hash)

Hi, I'm trying to bootstrap current Guix (master) from Guix past (1.1.0 binary tarball). The goal is: I want to have only guix-the-package-manager at a specific guix commit (!) available inside a Docker image. Because the package "guix" in guix is always behind a little bit, that means I have to

Re: Bootstrapping core-updates fails with mpc-1.2.1dev

I might have found the reason thanks to "guix build -K". Here are a few files in the gcc source directory: lrwxrwxrwx 1 andreas users 9 Aug 20 22:29 gmp -> gmp-6.0.0 drwxr-xr-x 15 andreas users4096 Aug 20 22:29 gmp-6.0.0/ lrwxrwxrwx 1 andreas users 9 Aug 20 22:29 mpc -> mpc-1.2.1

Bootstrapping core-updates fails with mpc-1.2.1dev

Hello, after the release of mpc-1.2.0, I tried to update the version in core-updates. More precisely, I used a tarball of the current master under the name of mpc-1.2.1dev, with an additional commit. Then bootstrapping fails. For someone with bayfront access, the build log is in /var/log

Re: Rust bootstrapping TODO

docs of the compilers used for bootstrapping. I guess this kind of change could go in a topic branch that we’d merge once IceCat is built. > (2) Bootstrap rust 1.29.0 directly via mrustc 0.9. > See https://github.com/thepowersgang/mrustc/issues/140 for why that is > currently not working.

Rust bootstrapping TODO

Hi, here a list of things we could still do in order to improve the Rust bootstrapping process. (1) For all Mozilla Rusts except the latest one, pass "--disable-docs --disable-compilerdocs" in order to disable building (and especially TESTING) the docs. Testing the docs takes a very

reproducibility and bootstrapping in mid 2019 (was Re: on cabal revisions)

#x27;t know the reproducibility situation with Stackage or Hackage defined packages (and web applications), I just hope it's better than this. Re. boostrapping, unfortunately we still have an unbootstrappable Haskell toolchain https://web.archive.org/web/20190615075205/http://www.joachim-breitner.de/

Re: bootstrapping SED-4.5, circular dependency?

Hi! Jan Nieuwenhuizen skribis: > Ludovic Courtès writes: > > Hello, > >> Jan, could it be that the ‘basename’ and ‘dirname’ implementations in >> Gash fail this test? It might be that sed is not needed if you get >> these right. > > Ah, yes! I have added some test to Gash and this > > base

Re: bootstrapping SED-4.5, circular dependency?

Ludovic Courtès writes: Hello, > Jan, could it be that the ‘basename’ and ‘dirname’ implementations in > Gash fail this test? It might be that sed is not needed if you get > these right. Ah, yes! I have added some test to Gash and this basename -- / failed, producing the empty string, wh

Re: bootstrapping SED-4.5, circular dependency?

Assaf Gordon writes: Hello Assaf, > Technically speaking, these kind of dependencies (e.g. needing SED > to build a package) arise from autotools, not directly from sed's > build commands. Ah yes, course. That is a big difference. >> Here is what I get: > [...] >> ERROR: In procedure scm-error

Re: bootstrapping SED-4.5, circular dependency?

Hello, Assaf Gordon skribis: > Digging a bit further, I see this specific sed program originates > from autoconf, from the M4 code used to implement basename and dirname, > e.g. here: > https://git.savannah.gnu.org/cgit/autoconf.git/tree/lib/m4sugar/m4sh.m4#n922 > https://git.savannah.gnu.org/cg

Re: bootstrapping SED-4.5, circular dependency?

GNU Guile. I would recommend adjusting your sed implementation to support these commands, because you'll encounter them in many packages that use autotools. Do you know whether bootstrapping of GZIP and/or SED is supported? It is supported in the sense that almost any old sed implementat

bootstrapping SED-4.5, circular dependency?

}\n\t /^X\\/\\(\\/\\/\\)$/{\n\ts//\\1/\n\tq\n\t }\n\t /^X\\/\\(\\/\\).*/{\n\ts//\\1/\n\tq\n\t }\n\t s/.*/./; q" --8<---cut here---end--->8--- The SED throwing this error is the minimal SED from Gash, that I implemented in GNU Gu

Re: A major milestone in bootstrapping

jerem...@pdp10.guru writes: > > Soon we hope to finish the MesCC bootstrap from M2-Planet and then we > will have a complete bootstrap path from 250byte hex0 all the way up to > gcc ^_^ Wow! Just Wow! I have a question though. It sounds like a bunch of this is assembly...Is assembly portable?

Re: [rb-general] A major milestone in bootstrapping

Orians, Jeremiah (DTMB) writes: >> Interesting... I'm looking at >> https://github.com/oriansj/M2-Planet/blob/master/seed.M1 >> How was it written? It seems like a monumental task to write all >> that and keep enough context in one's head! > Then again, I have >> never written assembly before...

RE: [rb-general] A major milestone in bootstrapping

> Interesting... I'm looking at > https://github.com/oriansj/M2-Planet/blob/master/seed.M1 > How was it written? It seems like a monumental task to write all that and > keep enough context in one's head! > Then again, I have never written > assembly before... If you'll notice https://github.co

Re: A major milestone in bootstrapping

jerem...@pdp10.guru writes: > Today I am proud to announce a combo of releases with major milestones. > > First stage0, reached Release version 0.2.0; which includes the following: > A 250byte hex0 bootstrap binary that is self-hosting and builds hex1, > which builds hex2, which bootstraps M0 macr

A major milestone in bootstrapping

Today I am proud to announce a combo of releases with major milestones. First stage0, reached Release version 0.2.0; which includes the following: A 250byte hex0 bootstrap binary that is self-hosting and builds hex1, which builds hex2, which bootstraps M0 macro assembly which has been used to make

Grafts vs. early bootstrapping packages

Hello, Mark H Weaver skribis: >> Ricardo Wurmus writes: [...] >> (define glibc-final >>;; The final glibc, which embeds the statically-linked Bash built above. >> - (package (inherit glibc-final-with-bootstrap-bash) >> + (package/inherit glibc-final-with-bootstrap-bash >> (name "g

Re: Bootstrapping Guix on HPC without Root

Hello! Wm Salt Hale skribis: > I have been attempting to install Guix on the University of > Washington's HPC using a modified bootstrapping script based on > https://github.com/pjotrp/nix-no-root > > The script can currently be found here (to be forked and pushed to G

Re: Bootstrapping Guix on HPC without Root

-0700, Wm Salt Hale wrote: > Hello, > > I have been attempting to install Guix on the University of > Washington's HPC using a modified bootstrapping script based on > https://github.com/pjotrp/nix-no-root > > The script can currently be found here (to be forked and pus

Bootstrapping Guix on HPC without Root

Hello, I have been attempting to install Guix on the University of Washington's HPC using a modified bootstrapping script based on https://github.com/pjotrp/nix-no-root The script can currently be found here (to be forked and pushed to GH when verified as working): https://communityda

Re: [PATCH 1/1] gnu: ncmpcpp: Remove bootstrapping inputs.

Leo Famulari skribis: > * gnu/packages/mpd.scm (ncmpcpp)[arguments]: Remove 'autogen' phase. > [native-inputs]: Remove autoconf, automake, and libtool. It’s a good idea. Maybe that was needed for an older version, or maybe that was never actually needed. Thanks! Ludo’.

[PATCH 1/1] gnu: ncmpcpp: Remove bootstrapping inputs.

* gnu/packages/mpd.scm (ncmpcpp)[arguments]: Remove 'autogen' phase. [native-inputs]: Remove autoconf, automake, and libtool. --- gnu/packages/mpd.scm | 14 ++ 1 file changed, 2 insertions(+), 12 deletions(-) diff --git a/gnu/packages/mpd.scm b/gnu/packages/mpd.scm index 63cb16f..4860

Bootstrapping

archive/html/guix-devel/2015-12/msg00107.html https://reproducible-builds.org/events/athens2015/bootstrapping/ Ludo’.

Re: Bootstrapping GHC

this if it’s possible. Blech. I find it worrisome if GHC doesn’t have a better bootstrapping story. How do they port it then? >>> 1. We’d have to host the binaries (step 2) somewhere and repeat the >>>process whenever the hash of ‘/bin/sh’ changes. How often will this >&g

Re: Bootstrapping GHC

> I don’t know GHC, but apparently it can be bootstrapped from > intermediate generated C files: > http://www.haskell.org/ghc/docs/6.4.1/html/building/sec-porting-ghc.html > Wouldn’t that be better than fiddling with binaries out-of-band? The recent versions of the compiler don’t support this.

Re: Bootstrapping GHC

Nikita Karetnikov skribis: > I’ve been thinking about GHC recently. (A quick reminder: there are > binary versions [1], but we can’t use them because some binaries point > to ‘/bin/sh’.) I believe the following should work for x86_64 and i686: I don’t know GHC, but apparently it can be bootstr

Bootstrapping GHC

I’ve been thinking about GHC recently. (A quick reminder: there are binary versions [1], but we can’t use them because some binaries point to ‘/bin/sh’.) I believe the following should work for x86_64 and i686: 1. We fetch the source version [2] (manually), adjust ‘/bin/sh’, and build everyth