From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Vincent Fazio <vfazio@xes-inc.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/busybox: redirect errors to /dev/null
Date: Wed, 2 Nov 2022 23:11:58 +0100 [thread overview]
Message-ID: <20221102231158.2ba5f486@windsurf> (raw)
In-Reply-To: <20221102215355.GB3918838@scaer>
On Wed, 2 Nov 2022 22:53:55 +0100
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> We did look at this together with Vincent back then.
>
> The issue is that pkg-config is called as part of BUSYBOX_CFLAGS and
> BUSYBOX_CFLAGS_busybox, which are part of BUSYBOX_MAKE_ENV, which will
> eventually be part of the environment when calling one of the kconfig
> frontends, like 'config' (when applying the configuration), or
> menuconfig et al.
>
> At that time, only parts of the PPD have been gathered, and not the
> parts needed to configure and build, so host-pkgconf is not rsynced to
> the busybox PPD.
But perhaps we should not pass those CFLAGS during the "configurator"
step?
Thomas
--
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:[~2022-11-02 22:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 23:50 [Buildroot] [PATCH 1/2] package/busybox: add patch to silence build errors Vincent Fazio
2022-10-07 23:50 ` [Buildroot] [PATCH 2/2] package/busybox: redirect errors to /dev/null Vincent Fazio
2022-11-01 22:41 ` Thomas Petazzoni via buildroot
2022-11-02 12:43 ` [Buildroot] [External] - " Vincent Fazio
2022-11-02 21:53 ` [Buildroot] " Yann E. MORIN
2022-11-02 22:11 ` Thomas Petazzoni via buildroot [this message]
2022-11-01 22:40 ` [Buildroot] [PATCH 1/2] package/busybox: add patch to silence build errors Thomas Petazzoni via buildroot
2022-11-02 22:00 ` Yann E. MORIN
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=20221102231158.2ba5f486@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=vfazio@xes-inc.com \
--cc=yann.morin.1998@free.fr \
/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