From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Heiko Thiery <heiko.thiery@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] configs/kontron_bl_imx8mm_defconfig: fix build failure with u-boot 2022.04
Date: Tue, 9 Aug 2022 10:06:02 +0200 [thread overview]
Message-ID: <20220809100602.2fb39e1c@windsurf> (raw)
In-Reply-To: <CAEyMn7Y+2=+2ruq-4+kvHqX2YXVNoGYLskYrYpjKfAxPfY2XOw@mail.gmail.com>
Hello Heiko,
On Tue, 9 Aug 2022 08:45:09 +0200
Heiko Thiery <heiko.thiery@gmail.com> wrote:
> Without the patch:
> --- 8< ---
> /usr/bin/gcc -O2 -isystem
> /home/hthiery/sources/mainline/buildroot/output/host/include
> -Wp,-MD,tools/.mkeficapsule.d -Wall -Wstrict-prototypes -O2
> -fomit-frame-pointer -std=gnu11 -DCONFIG_FIT_SIGNATURE
> -DCONFIG_FIT_SIGNATURE_MAX_SIZE=0xffffffff -DCONFIG_FIT_CIPHER
> -include ./include/compiler.h -idirafterinclude
> -idirafter./arch/arm/include -I./scripts/dtc/libfdt -I./tools
> -DUSE_HOSTCC -D__KERNEL_STRICT_NAMES -D_GNU_SOURCE -o
> tools/mkeficapsule tools/mkeficapsule.c -lgnutls -luuid
> --- 8< ---
>
> With the patch:
> --- 8< ---
> /usr/bin/gcc -O2 -isystem
> /home/hthiery/sources/mainline/buildroot/output/host/include
> -Wp,-MD,tools/.mkeficapsule.d -Wall -Wstrict-prototypes -O2
> -fomit-frame-pointer -std=gnu11 -DCONFIG_FIT_SIGNATURE
> -DCONFIG_FIT_SIGNATURE_MAX_SIZE=0xffffffff -DCONFIG_FIT_CIPHER
> -include ./include/compiler.h -idirafterinclude
> -idirafter./arch/arm/include -I./scripts/dtc/libfdt -I./tools
> -DUSE_HOSTCC -D__KERNEL_STRICT_NAMES -D_GNU_SOURCE -o
> tools/mkeficapsule tools/mkeficapsule.c
> -L/home/hthiery/sources/mainline/buildroot/output/host/lib -lgnutls
> -luuid
> --- 8< ---
>
> The -lgnuts and -luuid seems not to be sufficient. Using pkg-config
> will also add the -L<PATH-TO-LIBS>.
But this is not normal, because:
UBOOT_MAKE_OPTS += \
CROSS_COMPILE="$(TARGET_CROSS)" \
ARCH=$(UBOOT_ARCH) \
HOSTCC="$(HOSTCC) $(subst -I/,-isystem /,$(subst -I /,-isystem /,$(HOST_CFLAGS)))" \
HOSTLDFLAGS="$(HOST_LDFLAGS)" \
$(call qstrip,$(BR2_TARGET_UBOOT_CUSTOM_MAKEOPTS))
see we're passing HOSTLDFLAGS here? It contains -L$(HOST_DIR)/lib. So
it means there is also something wrong in U-Boot in that it doesn't use
$(HOSTLDFLAGS).
Best regards,
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-08-09 8:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-07 21:03 [Buildroot] [PATCH] configs/kontron_bl_imx8mm_defconfig: fix build failure with u-boot 2022.04 Heiko Thiery
2022-08-08 8:41 ` Thomas Petazzoni via buildroot
2022-08-09 6:45 ` Heiko Thiery
2022-08-09 8:06 ` Thomas Petazzoni via buildroot [this message]
2022-08-15 10:14 ` Thomas Petazzoni via buildroot
2022-08-23 17:30 ` Heiko Thiery
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=20220809100602.2fb39e1c@windsurf \
--to=buildroot@buildroot.org \
--cc=heiko.thiery@gmail.com \
--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