Re: [OE-core] [PATCH v2 0/1] u-boot-tools: drop yaml in DT validation

[Joao Marcos Costa <joaomarcos.costa@bootlin.com>]

Hello,

On 5/19/26 18:24, Michael Opdenacker wrote:
> Hi João Marcos
> 
> On 5/19/26 3:51 PM, Joao Marcos Costa wrote:
>> Hello again,
>>
>> On 5/18/26 21:12, Michael Opdenacker wrote:
>>> Hi João Marcos
>>>
>>> FYI, building the "qemuriscv64" machine is still broken on OE-core 
>>> (master), and it's seems likely to be related to this change;
>>>
>>> | /usr/bin/ld: scripts/dtc/yamltree.o: in function `dt_to_yaml':
>>> | yamltree.c:(.text+0x8fa): undefined reference to 
>>> `yaml_emitter_initialize'
>>> | /usr/bin/ld: yamltree.c:(.text+0x905): undefined reference to 
>>> `yaml_emitter_set_output_file'
>>> | /usr/bin/ld: yamltree.c:(.text+0x912): undefined reference to 
>>> `yaml_stream_start_event_initialize'
>>> | /usr/bin/ld: yamltree.c:(.text+0x91d): undefined reference to 
>>> `yaml_emitter_emit'
>> (...)
>>
>> This looks very much as the case described here:
>>
>> https://github.com/u-boot/u-boot/commit/807bcd844afeadbfe47ac132524cc7e3b699bc46
>>
>> Which could explain why it wasn't caught in the autobuilder, and why 
>> I'm not able to reproduce it in my container that does not natively 
>> provides this lib (i.e., no /usr/include/yaml.h).
> 
> 
> Indeed, I had the "libyaml-dev" package on my Debian 13 system, and the 
> problem goes away when I remove it.
> So, this explains why our autobuilder didn't catch this and I'm the only 
> one who seems to be impacted.
> 
> So, this is a U-Boot issue. However, I wonder why the problem is still 
> there while the above commit (present in 2026.04 that we're using) is 
> supposed to fix it...
> Thanks again
> Cheers
> Michael.

Well, yes, it was not a definitive solution. In fact, fixing this once 
and for all was originally the point of my patch, which is merged into 
u-boot's master, but not in 2026.04 tag.

-- 
Best regards,
João Marcos Costa