Closed KarlJoad closed 1 year ago
Well, that's an interesting error. I guess we need to explicitly return (values)
to denote a function that returns nothing? I'll admit this is part of the CL type system I know little about, but I would have guessed that a function that always returns nil
was the same as a function that returns nothing.
That looks to be a newer version of SBCL than is used in the pipeline, which is why it passed the last time it ran, but failed to build this time.
Afaiu nil and (values) are distinct. The problem is that in LOG-STRING the coee passes stream-fn a function that returns nil but the type of that function is declared as (function (stream) (values &optional))
One could either add (values) after the format call or update the ftype to have null as its return type
To help catch things like this earlier, I can add a package definition for Mahogany so people can do cd mahogany && guix build -f ./guix.scm
. That could be run in CI too (I'm not sure how, but I feel it should be possible.)
@KarlJoad, that would be appreciated! It looks like there are a couple of ways to get Guix working in a CI environment.
I am attempting to package Mahogany for Guix and am running into a compilation issue.
I have put all of my work so far on a personal branch of Guix: https://github.com/KarlJoad/guix/tree/mahogany
The full log is available as a GitHub Gist here