Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Joao Marcos Costa <joaomarcos.costa@bootlin.com>
To: richard.purdie@linuxfoundation.org, festevam@gmail.com,
	openembedded-core@lists.openembedded.org
Cc: khem.raj@oss.qualcomm.com, marek.vasut@mailbox.org
Subject: Re: [OE-core] [PATCH] u-boot: Fix u-boot-tools-native build after DTC update
Date: Wed, 29 Apr 2026 10:43:32 +0200	[thread overview]
Message-ID: <d322d9ea-5312-4033-a0fc-91abd7fd71cb@bootlin.com> (raw)
In-Reply-To: <516fab60f06521e2335185dc20d8b8c1d1330730.camel@linuxfoundation.org>

Hello,

On 4/29/26 10:03, Richard Purdie via lists.openembedded.org wrote:
> On Tue, 2026-04-28 at 21:18 -0300, Fabio Estevam via lists.openembedded.org wrote:
>> From: Marek Vasut <marek.vasut@mailbox.org>
>>
>> Set PKG_CONFIG_SYSROOT_DIR as invalid path, so the host tools
>> build will surely not find host /usr/include/yaml.h file and
>> will disable yamltree build. For details, see U-Boot commit
>> 807bcd844afe ("scripts/dtc: Fix pkg-config behavior under sysroot").
>>
>> Signed-off-by: Marek Vasut <marek.vasut@mailbox.org>
>> Signed-off-by: Fabio Estevam <festevam@gmail.com>
(...)
>>   
>> +# Set PKG_CONFIG_SYSROOT_DIR as invalid path, so the host tools
>> +# build will surely not find host /usr/include/yaml.h file and
>> +# will disable yamltree build. For details, see U-Boot commit
>> +# 807bcd844afe ("scripts/dtc: Fix pkg-config behavior under sysroot")
>> +PKG_CONFIG_SYSROOT_DIR:prepend = "/invalid/"
> 
> This feels a bit like a hack. Is there not a config option we can pass
> to u-boot to make this deterministic, i.e. always disable libyaml?
> 
> Cheers,
> 
> Richard

Maybe setting/appending "-DNO_YAML" at HOST_EXTRACFLAGS (e.g., through 
EXTRA_OEMAKE or BUILD_CFLAGS)?

In the end, that's a direct consequence of having an invalid 
PKG_CONFIG_SYSROOT_DIR:
https://github.com/u-boot/u-boot/blob/master/scripts/dtc/Makefile#L21

It is still kind of a hack, though, but I hope it helps!

-- 
Best regards,
João Marcos Costa


  parent reply	other threads:[~2026-04-29  8:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29  0:18 [PATCH] u-boot: Fix u-boot-tools-native build after DTC update Fabio Estevam
2026-04-29  8:03 ` [OE-core] " Richard Purdie
2026-04-29  8:36   ` Marek Vasut
2026-04-29  8:56     ` Richard Purdie
2026-04-29  9:47       ` Marek Vasut
2026-04-29  8:43   ` Joao Marcos Costa [this message]
2026-04-29  9:01     ` Quentin Schulz
2026-04-29  9:51       ` Marek Vasut
2026-04-29  9:54         ` Quentin Schulz
2026-04-29 13:55           ` Joao Marcos Costa

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=d322d9ea-5312-4033-a0fc-91abd7fd71cb@bootlin.com \
    --to=joaomarcos.costa@bootlin.com \
    --cc=festevam@gmail.com \
    --cc=khem.raj@oss.qualcomm.com \
    --cc=marek.vasut@mailbox.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /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