All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Vincent Fazio <vfazio@xes-inc.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/busybox: redirect errors to /dev/null
Date: Tue, 1 Nov 2022 23:41:38 +0100	[thread overview]
Message-ID: <20221101234138.66423cf3@windsurf> (raw)
In-Reply-To: <20221007235002.79221-2-vfazio@xes-inc.com>

Hello Vincent,

On Fri,  7 Oct 2022 18:50:02 -0500
Vincent Fazio <vfazio@xes-inc.com> wrote:

> When busybox.mk gets read, pkg-conf gets executed to determine the
> location of relevant libraries.
> 
> When Busybox is built with per-package directories enabled, a number of
> errors related to executing pkg-conf occur because directories have not
> been synced to provide pkg-confg at the point when it executes.

I don't get this. If pkg-config is executed before the per-package
directories are created... then how can pkg-config find libtirpc?

I just did a build of the following configuration:

BR2_arm=y
BR2_cortex_a9=y
BR2_ARM_ENABLE_VFP=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_TOOLCHAIN_EXTERNAL_BOOTLIN=y
BR2_PER_PACKAGE_DIRECTORIES=y
BR2_INIT_NONE=y
BR2_SYSTEM_BIN_SH_NONE=y
BR2_PACKAGE_BUSYBOX_SHOW_OTHERS=y
BR2_PACKAGE_LIBTIRPC=y
# BR2_TARGET_ROOTFS_TAR is not set

and I couldn't see the errors (but perhaps I missed them). Could you
provide an example configuration, the details of the error, and a
rationale as to why not finding libtirpc is not a problem when we in
fact expect to find it?

Thanks!

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

  reply	other threads:[~2022-11-01 22:41 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 [this message]
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
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=20221101234138.66423cf3@windsurf \
    --to=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=vfazio@xes-inc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.