From: Efraim Flashner <efraim@flashner.co.il>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 55373-done@debbugs.gnu.org,
denis 'gnutoo' carikli <gnutoo@cyberdimension.org>
Subject: bug#55373: efibootmgr fails to cross-compile: it looks for 'pkg-config' instead of 'TARGET-pkg-config'
Date: Sun, 15 May 2022 16:01:36 +0300 [thread overview]
Message-ID: <YoD5sFwo87kDWhxu@3900XT> (raw)
In-Reply-To: <362d12d7a221d3cda06d60067ecf80d332cc76a7.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]
On Wed, May 11, 2022 at 07:23:41PM +0200, Maxime Devos wrote:
> X-Debbugs-CC: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
>
> Title says it all.
>
> Also see the following excerpt from the build log:
>
> > make -f /tmp/guix-build-efibootmgr-17.drv-0/source/Make.deps deps SOURCES="efibootmgr.c efi.c unparse_path.c" SUBDIR_CFLAGS="-I/tmp/guix-build-efibootmgr-17.drv-0/source/src/include"
> > /gnu/store/4y5m9lb8k3qkb1y9m02sw9w9a6hacd16-bash-minimal-5.1.8/bin/sh: line 1: pkg-config: command not found
>
> Looks like PKG_CONFIG needs to be added to #:make-flags:
> <https://github.com/rhboot/efibootmgr/blob/892cb7444ce6f2cded9c67ff2ab3ef35a4c810c8/Make.rules#L64>.
>
> Maybe AR and CC as well.
>
I also needed to adjust efivar so it would refer to the correct gcc when
cross-compiling. Anyway, this should now be fixed.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-05-15 13:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 17:23 bug#55373: efibootmgr fails to cross-compile: it looks for 'pkg-config' instead of 'TARGET-pkg-config' Maxime Devos
2022-05-15 13:01 ` Efraim Flashner [this message]
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=YoD5sFwo87kDWhxu@3900XT \
--to=efraim@flashner.co.il \
--cc=55373-done@debbugs.gnu.org \
--cc=gnutoo@cyberdimension.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 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).