Skip to contentSkip to conversation

u-boot: Fix u-boot-tools-native build after DTC update

PATCH In review Fabio Estevam 5 participants 10 messages Apr 29

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 u-boot: Fix u-boot-tools-native build after DTC update

From: Marek Vasut <[email protected]>

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").

---
 meta/recipes-bsp/u-boot/u-boot-tools.inc | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)
meta/recipes-bsp/u-boot/u-boot-tools.inc +6 -1
index a055409c2cb0..071746b64e24 100644
@@ -1,5 +1,5 @@
 SUMMARY = "U-Boot bootloader tools"
-DEPENDS += "gnutls openssl util-linux swig-native libyaml-native"
+DEPENDS += "gnutls openssl util-linux swig-native"
 
 inherit python3native
 export STAGING_INCDIR = "${STAGING_INCDIR_NATIVE}"
@@ -88,3 +88,8 @@ RDEPENDS:${PN}:class-native = ""
 
 BBCLASSEXTEND = "native nativesdk"
 
+# 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/"
Signature · 1 line
2.43.0
#1 lore raw
Quoted 28 lines · Fabio Estevam via lists.openembedded.org

From: Marek Vasut <[email protected]>

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").

---
 meta/recipes-bsp/u-boot/u-boot-tools.inc | 7 ++++++-

 1 file changed, 6 insertions(+), 1 deletion(-)
meta/recipes-bsp/u-boot/u-boot-tools.inc +0 -0
index a055409c2cb0..071746b64e24 100644
@@ -1,5 +1,5 @@

 SUMMARY = "U-Boot bootloader tools"

meta/recipes-bsp/u-boot/u-boot-tools.inc +1 -1
-DEPENDS += "gnutls openssl util-linux swig-native libyaml-native"
+DEPENDS += "gnutls openssl util-linux swig-native"


 inherit python3native
 export STAGING_INCDIR = "${STAGING_INCDIR_NATIVE}"

meta/recipes-bsp/u-boot/u-boot-tools.inc +0 -0
@@ -88,3 +88,8 @@ RDEPENDS:${PN}:class-native = ""


 BBCLASSEXTEND = "native nativesdk"

meta/recipes-bsp/u-boot/u-boot-tools.inc RDEPENDS:${PN}:class-native = "" · line 95

Quoted 5 lines
meta/recipes-bsp/u-boot/u-boot-tools.inc +5 -0
+# 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

#2 lore raw
Quoted 29 lines · Richard Purdie
Quoted 28 lines · Fabio Estevam via lists.openembedded.org

From: Marek Vasut <[email protected]>

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").

---
  meta/recipes-bsp/u-boot/u-boot-tools.inc | 7 ++++++-
  1 file changed, 6 insertions(+), 1 deletion(-)
meta/recipes-bsp/u-boot/u-boot-tools.inc +1 -1
index a055409c2cb0..071746b64e24 100644
@@ -1,5 +1,5 @@
  SUMMARY = "U-Boot bootloader tools"
-DEPENDS += "gnutls openssl util-linux swig-native libyaml-native"
+DEPENDS += "gnutls openssl util-linux swig-native"
 
  inherit python3native
  export STAGING_INCDIR = "${STAGING_INCDIR_NATIVE}"
@@ -88,3 +88,8 @@ RDEPENDS:${PN}:class-native = ""
 
  BBCLASSEXTEND = "native nativesdk"
 
Quoted 8 lines

meta/recipes-bsp/u-boot/u-boot-tools.inc RDEPENDS:${PN}:class-native = "" · line 95

Quoted 5 lines
meta/recipes-bsp/u-boot/u-boot-tools.inc +5 -0
+# 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?

Currently there is not, but Linux did drop the whole yamltree part in ef8795f3f1ce ("dt-bindings: kbuild: Use DTB files for validation") and U-Boot should do the same. This path change is the minimum invasive change to achieve disabled yamltree with current U-Boot, until this is fixed upstream the same way Linux fixed it.

#3 lore raw
Quoted 38 lines · Marek Vasut
Quoted 29 lines · Richard Purdie
Quoted 28 lines · Fabio Estevam via lists.openembedded.org

From: Marek Vasut <[email protected]>

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").

---
  meta/recipes-bsp/u-boot/u-boot-tools.inc | 7 ++++++-

  1 file changed, 6 insertions(+), 1 deletion(-)
meta/recipes-bsp/u-boot/u-boot-tools.inc +0 -0
index a055409c2cb0..071746b64e24 100644
@@ -1,5 +1,5 @@

  SUMMARY = "U-Boot bootloader tools"

meta/recipes-bsp/u-boot/u-boot-tools.inc +1 -1
-DEPENDS += "gnutls openssl util-linux swig-native libyaml-native"
+DEPENDS += "gnutls openssl util-linux swig-native"


  inherit python3native
  export STAGING_INCDIR = "${STAGING_INCDIR_NATIVE}"

meta/recipes-bsp/u-boot/u-boot-tools.inc +0 -0
@@ -88,3 +88,8 @@ RDEPENDS:${PN}:class-native = ""


  BBCLASSEXTEND = "native nativesdk"

Quoted 8 lines

meta/recipes-bsp/u-boot/u-boot-tools.inc RDEPENDS:${PN}:class-native = "" · line 95

Quoted 5 lines
meta/recipes-bsp/u-boot/u-boot-tools.inc +5 -0
+# 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?

Quoted 5 lines

Currently there is not, but Linux did drop the whole yamltree part in ef8795f3f1ce ("dt-bindings: kbuild: Use DTB files for validation") and U-Boot should do the same. This path change is the minimum invasive change to achieve disabled yamltree with current U-Boot, until this is fixed upstream the same way Linux fixed it.

Lets just explicitly patch the code out then or something, I'm not sure we need to be minimally invasive here.

I really don't like hacks which people may copy/propagate and which can have interesting unintended side effects.

Cheers,

Richard

#4 lore raw
Quoted 45 lines · Richard Purdie
Quoted 38 lines · Marek Vasut
Quoted 29 lines · Richard Purdie
Quoted 28 lines · Fabio Estevam via lists.openembedded.org

From: Marek Vasut <[email protected]>

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").

---
   meta/recipes-bsp/u-boot/u-boot-tools.inc | 7 ++++++-
   1 file changed, 6 insertions(+), 1 deletion(-)
meta/recipes-bsp/u-boot/u-boot-tools.inc +1 -1
index a055409c2cb0..071746b64e24 100644
@@ -1,5 +1,5 @@
   SUMMARY = "U-Boot bootloader tools"
-DEPENDS += "gnutls openssl util-linux swig-native libyaml-native"
+DEPENDS += "gnutls openssl util-linux swig-native"
 
   inherit python3native
   export STAGING_INCDIR = "${STAGING_INCDIR_NATIVE}"
@@ -88,3 +88,8 @@ RDEPENDS:${PN}:class-native = ""
 
   BBCLASSEXTEND = "native nativesdk"
 
Quoted 8 lines

meta/recipes-bsp/u-boot/u-boot-tools.inc RDEPENDS:${PN}:class-native = "" · line 95

Quoted 5 lines
meta/recipes-bsp/u-boot/u-boot-tools.inc +5 -0
+# 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?

Quoted 5 lines

Currently there is not, but Linux did drop the whole yamltree part in ef8795f3f1ce ("dt-bindings: kbuild: Use DTB files for validation") and U-Boot should do the same. This path change is the minimum invasive change to achieve disabled yamltree with current U-Boot, until this is fixed upstream the same way Linux fixed it.

Quoted 5 lines

Lets just explicitly patch the code out then or something, I'm not sure we need to be minimally invasive here.

I really don't like hacks which people may copy/propagate and which can have interesting unintended side effects.

This is fine by me. Let me comment on the email from Quentin real quick with a bit more elaborate patch plan.

#5 lore raw
In reply to Richard Purdie

Hello,

Quoted 10 lines · Richard Purdie via lists.openembedded.org
Quoted 9 lines · Fabio Estevam via lists.openembedded.org

From: Marek Vasut <[email protected]>

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").

(...)

Quoted 10 lines

meta/recipes-bsp/u-boot/u-boot-tools.inc RDEPENDS:${PN}:class-native = "" · line 95

Quoted 6 lines
meta/recipes-bsp/u-boot/u-boot-tools.inc +5 -0
+# 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?

Quoted 3 lines

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!

Signature · 2 lines
Best regards,
João Marcos Costa
#6 lore raw

Hi,

Quoted 25 lines · Joao Marcos Costa via lists.openembedded.org

Hello,

Quoted 10 lines · Richard Purdie via lists.openembedded.org
Quoted 9 lines · Fabio Estevam via lists.openembedded.org

From: Marek Vasut <[email protected]>

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").

(...)

Quoted 11 lines

meta/recipes-bsp/u-boot/u-boot-tools.inc RDEPENDS:${PN}:class-native = "" · line 95

Quoted 5 lines
meta/recipes-bsp/u-boot/u-boot-tools.inc +5 -0
+# 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,

Quoted 9 lines
Quoted 1 line

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://eur02.safelinks.protection.outlook.com/? url=https%3A%2F%2Fgithub.com%2Fu-boot%2Fu- boot%2Fblob%2Fmaster%2Fscripts%2Fdtc%2FMakefile%23L21&data=05%7C02%7Cquentin.schulz%40cherry.de%7C73feb8ea44e0468f38ea08dea5cb6a9f%7C5e0e1b5221b54e7b83bb514ec460677e%7C0%7C0%7C639130490251925693%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=%2BbKkw2HVgw52EWv%2FxeSlWRZ%2Ba3%2F3ireKwMxCLBvIwyg%3D&reserved=0

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

dtc-objs will still contain yamltree and thus attempt to build it.

Fabio, you are not explaining why you don't want to add the libyaml dependency, Khem attempted to add it in https://lore.kernel.org/openembedded-core/[email protected]/ but I don't see any follow-up or statement it should be dropped.

I'm very much against setting a variable in the recipe that applies to all version of the recipes and will not be looked at again. Instead, add a patch for U-Boot that removes this (but again, why?) logic so that next time we do an upgrade there are more chances of someone looking at patches and trying to figure out if they are still needed.

In any case, we absolutely need a justification otherwise I'm afraid we'll never be able to do a cleanup because we don't know why it was needed in the first place. This is something that has happened already enough time for me in OE-Core/YP that it really is a PITA for upgrades and cleanups.

Cheers,
Quentin

#7 lore raw
Quoted 38 lines · Quentin Schulz

Hi,

Quoted 25 lines · Joao Marcos Costa via lists.openembedded.org

Hello,

Quoted 10 lines · Richard Purdie via lists.openembedded.org
Quoted 9 lines · Fabio Estevam via lists.openembedded.org

From: Marek Vasut <[email protected]>

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").

(...)

Quoted 11 lines

meta/recipes-bsp/u-boot/u-boot-tools.inc RDEPENDS:${PN}:class-native = "" · line 95

Quoted 5 lines
meta/recipes-bsp/u-boot/u-boot-tools.inc +5 -0
+# 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,

Quoted 9 lines
Quoted 1 line

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://eur02.safelinks.protection.outlook.com/? url=https%3A%2F%2Fgithub.com%2Fu-boot%2Fu- boot%2Fblob%2Fmaster%2Fscripts%2Fdtc%2FMakefile%23L21&data=05%7C02%7Cquentin.schulz%40cherry.de%7C73feb8ea44e0468f38ea08dea5cb6a9f%7C5e0e1b5221b54e7b83bb514ec460677e%7C0%7C0%7C639130490251925693%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=%2BbKkw2HVgw52EWv%2FxeSlWRZ%2Ba3%2F3ireKwMxCLBvIwyg%3D&reserved=0

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

Quoted 7 lines

dtc-objs will still contain yamltree and thus attempt to build it.

Fabio, you are not explaining why you don't want to add the libyaml dependency, Khem attempted to add it in https://lore.kernel.org/ openembedded-core/[email protected]/ but I don't see any follow-up or statement it should be dropped.

I'm very much against setting a variable in the recipe that applies to all version of the recipes and will not be looked at again. Instead, add a patch for U-Boot that removes this (but again, why?) logic so that next time we do an upgrade there are more chances of someone looking at patches and trying to figure out if they are still needed.

In any case, we absolutely need a justification otherwise I'm afraid we'll never be able to do a cleanup because we don't know why it was needed in the first place. This is something that has happened already enough time for me in OE-Core/YP that it really is a PITA for upgrades and cleanups.

In short, see the U-Boot commit 807bcd844afe ("scripts/dtc: Fix pkg-config behavior under sysroot") referenced in the commit message of this patch, and the matching Linux kernel commit ef8795f3f1ce ("dt-bindings: kbuild: Use DTB files for validation") .

I think we need to port that kernel commit to U-Boot, upstream that kernel commit (should be easy) and then add it here into OE too. Then it will be really a problem solved all over the place and case closed.

#8 lore raw

Hi Marek,

Quoted 39 lines · Marek Vasut
Quoted 38 lines · Quentin Schulz

Hi,

Quoted 34 lines · Joao Marcos Costa via lists.openembedded.org

Hello,

Quoted 10 lines · Richard Purdie via lists.openembedded.org
Quoted 9 lines · Fabio Estevam via lists.openembedded.org

From: Marek Vasut <[email protected]>

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").

(...)

Quoted 9 lines

meta/recipes-bsp/u-boot/u-boot-tools.inc RDEPENDS:${PN}:class-native = "" · line 95

Quoted 5 lines
meta/recipes-bsp/u-boot/u-boot-tools.inc +5 -0
+# 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?

Quoted 3 lines

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://eur02.safelinks.protection.outlook.com/? url=https%3A%2F%2Fgithub.com%2Fu-boot%2Fu- boot%2Fblob%2Fmaster%2Fscripts%2Fdtc%2FMakefile%23L21&data=05%7C02%7Cquentin.schulz%40cherry.de%7C73feb8ea44e0468f38ea08dea5cb6a9f%7C5e0e1b5221b54e7b83bb514ec460677e%7C0%7C0%7C639130490251925693%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=%2BbKkw2HVgw52EWv%2FxeSlWRZ%2Ba3%2F3ireKwMxCLBvIwyg%3D&reserved=0

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

Quoted 9 lines
Quoted 7 lines

dtc-objs will still contain yamltree and thus attempt to build it.

Fabio, you are not explaining why you don't want to add the libyaml dependency, Khem attempted to add it in https:// eur02.safelinks.protection.outlook.com/? url=https%3A%2F%2Flore.kernel.org%2F&data=05%7C02%7Cquentin.schulz%40cherry.de%7C51022e2ce9de4d74fada08dea5d4e18f%7C5e0e1b5221b54e7b83bb514ec460677e%7C0%7C0%7C639130530938248835%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=fXgk4FZc6wnMD37AUWBnyJQBwmuAnjURis5JlZnT9iM%3D&reserved=0 openembedded-core/[email protected]/ but I don't see any follow-up or statement it should be dropped.

I'm very much against setting a variable in the recipe that applies to all version of the recipes and will not be looked at again. Instead, add a patch for U-Boot that removes this (but again, why?) logic so that next time we do an upgrade there are more chances of someone looking at patches and trying to figure out if they are still needed.

In any case, we absolutely need a justification otherwise I'm afraid we'll never be able to do a cleanup because we don't know why it was needed in the first place. This is something that has happened already enough time for me in OE-Core/YP that it really is a PITA for upgrades and cleanups.

In short, see the U-Boot commit 807bcd844afe ("scripts/dtc: Fix pkg- config behavior under sysroot") referenced in the commit message of this patch, and the matching Linux kernel commit ef8795f3f1ce ("dt-bindings: kbuild: Use DTB files for validation") .

I know, I brought this up here: https://lore.kernel.org/openembedded-core/[email protected]/

Quoted 1 line

I think we need to port that kernel commit to U-Boot, upstream that kernel commit (should be easy) and then add it here into OE too. Then it will be really a problem solved all over the place and case closed.

Yes, someone needs to do the work.

Cheers,
Quentin

#9 lore raw

Hello,

(...)

Quoted 11 lines
Quoted 2 lines

In short, see the U-Boot commit 807bcd844afe ("scripts/dtc: Fix pkg- config behavior under sysroot") referenced in the commit message of this patch, and the matching Linux kernel commit ef8795f3f1ce ("dt-bindings: kbuild: Use DTB files for validation") .

I know, I brought this up here: https://lore.kernel.org/openembedded-core/[email protected]/

Quoted 1 line

I think we need to port that kernel commit to U-Boot, upstream that kernel commit (should be easy) and then add it here into OE too. Then it will be really a problem solved all over the place and case closed.

Yes, someone needs to do the work.

Cheers,
Quentin

Just in case, I wrote the patch for that, and started the build to test it. Once I'm done testing, I will send it here and to U-Boot's mailing list as well.

Signature · 2 lines
Best regards,
João Marcos Costa