Re: [Buildroot] [PATCH 2/2] package/busybox: redirect errors to /dev/null

[Thomas Petazzoni via buildroot <buildroot@buildroot.org>]

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