guix-comm...@gnu.org writes: > This is an automated email from the git hooks/post-receive script. > > efraim pushed a commit to branch master > in repository guix. > > The following commit(s) were added to refs/heads/master by this push: > new 2a6d2fc1d8 gnu: sbcl: fix build on riscv64-linux. > 2a6d2fc1d8 is described below > > commit 2a6d2fc1d8e3434e283d6d2e559529b41a242fea > Author: Efraim Flashner <efr...@flashner.co.il> > AuthorDate: Wed Jun 7 09:55:35 2023 +0300 > > gnu: sbcl: fix build on riscv64-linux. > > * gnu/packages/patches/sbcl-riscv-Make-contribs-build-again.patch: New > file. > * gnu/local.mk(dist_patch_DATA): register it. > * gnu/packages/lisp.scm (sbcl): [source]<patches>: Use it here. > --- > gnu/local.mk | 1 + > gnu/packages/lisp.scm | 3 + > .../sbcl-riscv-Make-contribs-build-again.patch | 71 > ++++++++++++++++++++++ > 3 files changed, 75 insertions(+)
Did this change need to go straight to master? → guix refresh -l sbcl Building the following 314 packages would ensure 1615 dependent packages are rebuilt: ... To me that says to be that this would be appropriate for staging [1]. 1: https://guix.gnu.org/manual/devel/en/html_node/Submitting-Patches.html#index-rebuild-scheduling-strategy Maybe this would be OK if the patch was applied in such a way that it only affects riscv64-linux, but it isn't, so this affects all systems.
signature.asc
Description: PGP signature
