From: Josselin Poiret via Guix-patches via <guix-patches@gnu.org>
To: 55602@debbugs.gnu.org
Cc: Josselin Poiret <dev@jpoiret.xyz>
Subject: [bug#55602] [PATCH 0/2] Move (gnu platform) and friends to guix, and fix linux module build system.
Date: Mon, 23 May 2022 22:29:02 +0200 [thread overview]
Message-ID: <20220523202902.32411-1-dev@jpoiret.xyz> (raw)
Hi everyone,
The linux-module-build-system broke because we're now using platform
records, and the accessor platform-glibc-dynamic-linker is syntax.
The build system cannot invoke it through module-ref shenanigans (done
previously to avoid some circular dependencies), because as everyone
knows syntax expands at compile/expand-time only. Since the platform
code has moved to its own cozy (gnu platform) in the meantime, I
figured that it could very well be simply use-module'd, but then it'd
have to end up in (guix ...) to follow the rule that guix modules
should never directly use-module gnu modules. Hence this quite big
patchset.
This addresses the same issue as [1].
[1] https://issues.guix.gnu.org/55591
Best,
Josselin Poiret (2):
Move (gnu platform) and (gnu platforms ...) to guix/.
build-system: linux-module: Directly use-module (guix platform).
doc/guix.texi | 2 +-
etc/release-manifest.scm | 2 +-
gnu/ci.scm | 2 +-
gnu/image.scm | 2 +-
gnu/local.mk | 8 --------
gnu/packages/bioinformatics.scm | 2 +-
gnu/packages/bootstrap.scm | 2 +-
gnu/packages/cross-base.scm | 2 +-
gnu/packages/instrumentation.scm | 2 +-
gnu/packages/linux.scm | 2 +-
gnu/system/image.scm | 2 +-
gnu/system/images/hurd.scm | 2 +-
gnu/system/images/novena.scm | 2 +-
gnu/system/images/pine64.scm | 2 +-
gnu/system/images/pinebook-pro.scm | 2 +-
gnu/system/images/rock64.scm | 2 +-
guix/build-system/linux-module.scm | 4 ++--
{gnu => guix}/platform.scm | 4 ++--
{gnu => guix}/platforms/arm.scm | 5 ++---
{gnu => guix}/platforms/hurd.scm | 5 ++---
{gnu => guix}/platforms/mips.scm | 5 ++---
{gnu => guix}/platforms/powerpc.scm | 5 ++---
{gnu => guix}/platforms/riscv.scm | 5 ++---
{gnu => guix}/platforms/s390.scm | 5 ++---
{gnu => guix}/platforms/x86.scm | 5 ++---
guix/scripts/build.scm | 2 +-
guix/scripts/system.scm | 2 +-
guix/self.scm | 2 +-
28 files changed, 36 insertions(+), 51 deletions(-)
rename {gnu => guix}/platform.scm (98%)
rename {gnu => guix}/platforms/arm.scm (92%)
rename {gnu => guix}/platforms/hurd.scm (90%)
rename {gnu => guix}/platforms/mips.scm (90%)
rename {gnu => guix}/platforms/powerpc.scm (92%)
rename {gnu => guix}/platforms/riscv.scm (91%)
rename {gnu => guix}/platforms/s390.scm (90%)
rename {gnu => guix}/platforms/x86.scm (94%)
--
2.36.0
next reply other threads:[~2022-05-23 20:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 20:29 Josselin Poiret via Guix-patches via [this message]
2022-05-23 20:37 ` [bug#55602] [PATCH v2 0/2] Move (gnu platform) and friends to guix, and fix linux module build system Josselin Poiret via Guix-patches via
2022-05-23 20:37 ` [bug#55602] [PATCH v2 1/2] Move (gnu platform) and (gnu platforms ...) to guix/ Josselin Poiret via Guix-patches via
2022-05-23 20:37 ` [bug#55602] [PATCH v2 2/2] build-system: linux-module: Directly use-module (guix platform) Josselin Poiret via Guix-patches via
2022-05-25 7:31 ` bug#55602: [PATCH 0/2] Move (gnu platform) and friends to guix, and fix linux module build system Mathieu Othacehe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220523202902.32411-1-dev@jpoiret.xyz \
--to=guix-patches@gnu.org \
--cc=55602@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).