[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Latest Commit: error: linux-libre-headers-6.8: unbound variable 71c6
From: |
Wilko Meyer |
Subject: |
Re: Latest Commit: error: linux-libre-headers-6.8: unbound variable 71c678a16aae416298a0e3fa322b425315bb7b00 |
Date: |
Mon, 17 Jun 2024 21:53:39 +0200 |
This should fix it for now:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=71617
to prevent this from happening: the idea to use a generic
linux-libre-headers variable that points to the latest headers for these
cases came up in IRC, however:
#+BEGIN_SRC scheme
;; The following package is used in the early bootstrap, and thus must be kept
;; stable and with minimal build requirements.
(define-public linux-libre-headers-5.15.49
(make-linux-libre-headers "5.15.49" "gnu"
"13zqdcm4664vh7g57sxbfrlpsxm7zrma72mxdfdz7d9yndy2gfv8"))
(define-public linux-libre-headers linux-libre-headers-5.15.49)
#+END_SRC
it seems like early bootstrap depends on it being at 5.15.49. I do not
know enough about the early bootstrap process to be able to tell wether
this applies for linux-libre-headers-5.15.49 and linux-libre-headers or
just to the former. Maybe someone more knowledgable on this could tell
wether or not it is safe to update linux-libre-headers to a more recent
version (as this would be useful for such cases)?
--
Kind regards,
Wilko Meyer
w@wmeyer.eu