Hi Mathieu, Mathieu Othacehe <[email protected]> skribis:
>> I believe this is fixed by commit >> 20ed093977cc80ba1729c38e05ae7955a38069a6, which follows a modification >> to the ‘source-module-closure’ so that callers can catch >> missing-dependency errors. >> >> Please let me know what you think! > > It seems ok, thanks for fixing it ! > >> >> After that, you should be able to reinstate the (guix git) commit, >> provided build-aux/build-self.scm does: >> >> (define guile-git >> (package-for-current-guile "guile-git" >> "guile2.2-git" >> "guile2.0-git")) > ^ > for guile2.0-git, > we need to define guile2.0-bytestructures, so I tried to package it, > and I get the following error : > > ice-9/boot-9.scm:109:20: In procedure #<procedure 9dbe40 at > ice-9/boot-9.scm:100:6 (thrown-k . > ice-9/boot-9.scm:109:20: re-exporting local variable: cstring-pointer > > It is something introduced in bytestructures commit 91d042e, that works > on 2.2 but not on 2.0, I have no idea why ! It would be nice to have guile2.0-git, but note that it does not *have* to exist: ‘package-for-current-guile’ returns #f if none of the packages exists, and (guix build pull) skips modules that lack their dependencies. So I would first suggest to re-add (guix git), and later see with Amirouche et al. what could be done to get Guile-Git on 2.0. Does that make sense? Thanks, Ludo’.
