unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Pierre Langlois <pierre.langlois@gmx.com>
Cc: "Sébastien Lerique" <sl@eauchat.org>, 54595@debbugs.gnu.org
Subject: [bug#54595] [PATCH 2/2] gnu: libfido2: Fix cross-compilation.
Date: Sun, 27 Mar 2022 17:43:35 +0200	[thread overview]
Message-ID: <1fd85fd1bd5389fbe4f14325e22fac8705b9807b.camel@telenet.be> (raw)
In-Reply-To: <871qyn7afq.fsf@gmx.com>

[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]

Pierre Langlois schreef op zo 27-03-2022 om 15:04 [+0100]:
> I'm also not entirely sure if it's
> #+pkg-config or #$pkg-config, both seem to work

#+pkg-config, given that it is a thing that needs to be run during
compilation.  I'm wondering, do you have transparant QEMU emulation
enabled?  If so, both seeming to work is expected since QEMU will
emulate the cross-compiled cross-compiling (IIUC a canadian cross, in
GCC terminology) pkg-config.  If not, I would expect some kind of error
...

Or, to allow for package transformations:

  #+(file-append (this-package-native-input (pkg-config-for-target))
                 "/bin/" (pkg-config-for-target))

though maybe package transformations should just transform the G-exp as
well, dunno.  ('file-append' is not strictly required here.)  Maybe we can
have a macro (pkg-config-binary) that expands to that thing, and
use it in other packages?

Possibly interesting or irrelevant: the following will produce an
x86_64-linux-gnu-pkg-config that can be run on a aarch64-linux-gnu
computer to find libraries for x86_64-linux-gnu.

$ guix build -e '(parameterize (((@ (guix utils) %current-target-system) "x86_64-linux-gnu")) (@ (gnu packages pkg-config) pkg-config))' --target=aarch64-linux-gnu

Greetings,
Maxime.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-03-27 15:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-27 12:28 [bug#54595] [PATCH 0/2] Fix cross-compilation for libfido2 Sébastien Lerique
2022-03-27 12:29 ` [bug#54595] [PATCH 1/2] gnu: libfido2: Use new style Sébastien Lerique
2022-03-27 12:29   ` [bug#54595] [PATCH 2/2] gnu: libfido2: Fix cross-compilation Sébastien Lerique
2022-03-27 12:36     ` Maxime Devos
2022-03-27 13:01       ` Sébastien Lerique
2022-03-27 14:04       ` Pierre Langlois
2022-03-27 15:43         ` Maxime Devos [this message]
2022-03-27 17:27           ` Pierre Langlois
2022-03-27 18:00             ` Maxime Devos
2022-03-27 22:12               ` Thiago Jung Bauermann via Guix-patches via
2022-03-27 15:44         ` Maxime Devos
2022-03-27 13:00 ` [bug#54595] [PATCH v2 1/2] gnu: libfido2: Use new style Sébastien Lerique
2022-03-27 13:00   ` [bug#54595] [PATCH v2 2/2] gnu: libfido2: Fix cross-compilation Sébastien Lerique
2022-03-27 14:09     ` Maxime Devos

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=1fd85fd1bd5389fbe4f14325e22fac8705b9807b.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=54595@debbugs.gnu.org \
    --cc=pierre.langlois@gmx.com \
    --cc=sl@eauchat.org \
    /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).