From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 57127@debbugs.gnu.org, andrewpatt7@gmail.com
Subject: bug#57127: unzip fails to cross-compile
Date: Thu, 11 Aug 2022 10:12:47 +0000 [thread overview]
Message-ID: <0714DAB3-DDD7-47E9-B41E-BE571378F54C@tobias.gr> (raw)
In-Reply-To: <87y1vvoecx.fsf@gmail.com>
Hi Andrew,
This is a bug in Guix, not really related to cross-compiling (hence you can stop cross-testing and reporting different architectures, although the effort is appreciated!).
%output is practically deprecated, but is still present in a good number of packages. Sometimes it happens to work, because a specific build system explicitly kept support for it. Some build systems don't, making support for it feel unreliable. It is. %output is obsolete for new code.
What also happens is that build systems still support it in the well-tested native build path, but not when cross-compiling. That seems to be the case here.
> Interestingly, it gives the same errors when explicitly building for x86_64
> on an x86_64 machine, even though I would expect doing so to compile as normal.
You don't define what you mean by 'explicitly building'.
If you mean --target=x86_64-linux-gnu, why would it not fail? You're cross-compiling. Guix doesn't silently fall back to a non-cross build when the architectures match, no should it IMO.
The fix should be simple: rewrite unzip to use gexps and hence #$output. Why didn't I simply do so yet? Because too many packages depend on unzip to simply do so on master. There's probably a way around that, but I'll try it when I'm back at a computer.
Kind regards,
T G-R
Sent on the go. Excuse or enjoy my brevity.
next prev parent reply other threads:[~2022-08-11 10:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 22:06 bug#57127: unzip fails to cross-compile Andrew Patterson
2022-08-11 0:45 ` Andrew Patterson
2022-08-11 8:48 ` Maxime Devos
2022-08-11 10:12 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2022-08-11 10:28 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-08-11 18:11 ` Andrew Patterson
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=0714DAB3-DDD7-47E9-B41E-BE571378F54C@tobias.gr \
--to=bug-guix@gnu.org \
--cc=57127@debbugs.gnu.org \
--cc=andrewpatt7@gmail.com \
--cc=me@tobias.gr \
/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).