From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
Buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH] Revert "package/gnupg2: bump to version 2.4.0"
Date: Sat, 18 Feb 2023 14:24:35 +0100 [thread overview]
Message-ID: <20230218142435.06cb9c26@windsurf> (raw)
In-Reply-To: <96015d0268df72d3cdd58e7db09c1333@free.fr>
Hello Julien,
On Sat, 18 Feb 2023 12:13:16 +0100
Julien Olivain <ju.o@free.fr> wrote:
> I indeed started to receive some autobuild failures.
> Unfortunately, I cannot reproduce on my system for now:
> on my side, the build complete successfully.
>
> I tried with _and_ without having a /usr/bin/gpgrt-config on host,
> which I was suspecting to bring some host config.
>
> In my first proposal of gnupg2 version 2.4.0 bump [1], I initially
> proposed
> to add Buildroot staging bin dir in PATH, to make sure we won't have
> such
> host/br-staging confusion:
>
> GNUPG2_CONF_ENV = PATH=$(STAGING_DIR)/usr/bin:$(BR_PATH)
This is a really bad idea, and can potentially break. Indeed,
STAGING_DIR/usr/bin contains lots of programs that are compiled for the
target. So if you do that, the build process on your build machine
might try to invoke executables that are compiled for the target.
If the issue comes from a <foo>-config script, then generally, two
things are needed:
- Make sure the <foo>-config script returns correct values for
cross-compilation. If not, use <pkg>_CONFIG_SCRIPTS in the package
installing this <foo>-config script
- Make sure the package calling the <foo>-config script calls the
right one. Most autotools-based projects provide some sort of cache
variable that allows to tell the configure script that <foo>-config
in $(STAGING_DIR)/usr/bin/<foo>-config should be used
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-02-18 13:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-18 10:14 [Buildroot] [PATCH] Revert "package/gnupg2: bump to version 2.4.0" Bagas Sanjaya
2023-02-18 10:39 ` Thomas Petazzoni via buildroot
2023-02-18 11:13 ` Julien Olivain
2023-02-18 13:24 ` Thomas Petazzoni via buildroot [this message]
2023-02-18 13:45 ` [Buildroot] Debugging gnupg2 unsafe search path error (was Re: [PATCH] Revert "package/gnupg2: bump to version 2.4.0") Bagas Sanjaya
2023-02-18 17:40 ` Julien Olivain
2023-02-19 4:26 ` Bagas Sanjaya
2023-02-19 15:00 ` Julien Olivain
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=20230218142435.06cb9c26@windsurf \
--to=buildroot@buildroot.org \
--cc=bagasdotme@gmail.com \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox