From: pukkamustard <pukkamustard@posteo.net>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 57055@debbugs.gnu.org
Subject: [bug#57055] [PATCH 2/2] gnu: Add guile-srfi-146.
Date: Tue, 09 Aug 2022 09:24:06 +0000 [thread overview]
Message-ID: <86lerx7on3.fsf@posteo.net> (raw)
In-Reply-To: <4db0fbfe-ac09-e8fa-d16a-140d33bbd871@telenet.be>
Maxime Devos <maximedevos@telenet.be> writes:
> I don't know about guile-build-system, but for some Guile packages
> that use gnu-build-system, the package itself has to be added to
> native-inputs when cross-compiling (this-package may be useful). I
> think it has something to do with macros and the module system.
That seems to do the trick. Adding the Guile libraries to the
native-inputs makes cross-compilation work.
I will send in a V2 of patches that fixes this.
Thanks,
pukkamustard
next prev parent reply other threads:[~2022-08-09 9:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 8:32 [bug#57055] [PATCH 0/2] gnu: Add guile-srfi-146 pukkamustard
2022-08-08 8:36 ` [bug#57055] [PATCH 1/2] gnu: Add guile-srfi-128 pukkamustard
2022-08-08 8:36 ` [bug#57055] [PATCH 2/2] gnu: Add guile-srfi-146 pukkamustard
2022-08-08 9:30 ` Maxime Devos
2022-08-08 12:43 ` pukkamustard
2022-08-08 13:12 ` ( via Guix-patches via
2022-08-08 13:47 ` pukkamustard
2022-08-08 18:22 ` Maxime Devos
2022-08-19 13:41 ` pukkamustard
2022-08-19 20:34 ` Maxime Devos
2022-08-29 8:48 ` pukkamustard
2022-08-08 19:04 ` Maxime Devos
2022-08-09 9:24 ` pukkamustard [this message]
2022-08-09 9:30 ` [bug#57055] [PATCH v2 1/2] gnu: Add guile-srfi-128 pukkamustard
2022-08-09 9:30 ` [bug#57055] [PATCH v2 2/2] gnu: Add guile-srfi-146 pukkamustard
2022-08-29 8:55 ` [bug#57055] [PATCH v3 1/2] gnu: Add guile-srfi-128 pukkamustard
2022-08-29 8:56 ` [bug#57055] [PATCH v3 2/2] gnu: Add guile-srfi-146 pukkamustard
2022-08-31 21:14 ` bug#57055: [PATCH 0/2] " Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86lerx7on3.fsf@posteo.net \
--to=pukkamustard@posteo.net \
--cc=57055@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.