From: Maxime Devos <maximedevos@telenet.be>
To: L p R n d n <guix@lprndn.info>, 52574@debbugs.gnu.org
Subject: bug#52574: Cross-compiling glib failure
Date: Fri, 17 Dec 2021 21:40:17 +0000 [thread overview]
Message-ID: <befb94870e8bf96380d1ee690e0c36912e90b327.camel@telenet.be> (raw)
In-Reply-To: <87k0g3fl7c.fsf@lprndn.info>
L p R n d n schreef op vr 17-12-2021 om 12:51 [+0000]:
>
> Hello guix,
>
> Trying to cross-compile glib to aarch64with:
>
> guix build --target=aarch64-linux-gnu glib
>
> I get this error:
>
> `Unbound variable: %outputs
>
> I suppose the glib’s definition needs to be adapted to Guix’s new
> style
> which was merged a few days ago?
>
Actually, glib's build system (meson-build-system) did not support
cross-compilation at all before the merge. Cross-compilation support
was added on that branch, but glib's package broke later, presumably in
<https://git.savannah.gnu.org/cgit/guix.git/commit/?id=f22f6fc3b6cc6382df3246d192a40a3951b48c37>.
The fix would be to replace to wrap the configure flags in a #~,
instead of a ´,replace (assoc-ref %outputs "bin") by #$output:bin and
adjust the configure flags of glib-with-documentation to use #~ and #$
instead of ´ and ,.
To avoid rebuilds, some
(if (%current-target-system) #~#$output:bin #~(assoc-ref %outputs
"bin"))
may be needed.
Greetings,
Maxime.
next prev parent reply other threads:[~2021-12-17 21:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 12:51 bug#52574: Cross-compiling glib failure L p R n d n
2021-12-17 21:40 ` Maxime Devos [this message]
2021-12-18 4:34 ` Maxim Cournoyer
2021-12-19 22:12 ` Ludovic Courtès
2021-12-20 4:55 ` Maxim Cournoyer
[not found] ` <c39f3277b9e7c71a2d710b81e9468db640f47b63.camel@telenet.be>
2021-12-21 9:04 ` Ludovic Courtès
2022-01-17 17:14 ` Maxim Cournoyer
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=befb94870e8bf96380d1ee690e0c36912e90b327.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=52574@debbugs.gnu.org \
--cc=guix@lprndn.info \
/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).