All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>,
	Christian Stewart <christian@aperture.us>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 3/3] boot/uboot: add host-python-pylibfdt dependency if needed
Date: Mon, 31 Jul 2023 16:43:21 +0200	[thread overview]
Message-ID: <20230731164321.615664d5@windsurf> (raw)
In-Reply-To: <a9b895f5-5136-6d92-34a7-ada38a3da21f@benettiengineering.com>

On Mon, 31 Jul 2023 16:10:48 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:

> U-Boot approach for this is to force Python3 to build libfdtpy[1]
> but what we experience here is a consequence of Buildroot's commit 
> 231d79c81e9a1f8c2ef14861374a40fcdc5e6b33 [2]
> 
> Something happens after that patch has been applied that basically
> passes Buildroot's host dtc to UBOOT_MAKE_OPTS:
> ```
> UBOOT_MAKE_OPTS += DTC=$(HOST_DIR)/bin/dtc
> ```
> The root cause seems to be Python3 anyway as U-Boot patch points.
> 
> Since we can't patch every U-Boot version we could fix Python3 but
> using the approach proposed by Christian is easier to be honest.
> 
> To prove it's a Python3 issue you can see from one of my Gitlab-CI
> failure[3] that various U-Boot versions are different, not the last
> one(2023.07).

Hm, thanks for your feedback, but even after reading 3 times your
e-mail, I still don't grasp what's going on. You've pointed out that
Buildroot commit 231d79c81e9a1f8c2ef14861374a40fcdc5e6b33 is when build
failures starting to occur. But what's the relationship between setting
DTC and U-Boot having issues finding pylibfdt?

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

  reply	other threads:[~2023-07-31 14:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-26 20:28 [Buildroot] [PATCH v1 1/3] package/python-pylibfdt: bump version to 1.7.0.post1 Christian Stewart via buildroot
2023-07-26 20:28 ` [Buildroot] [PATCH v1 2/3] package/python-pylibfdt: add host python package Christian Stewart via buildroot
2023-08-06 11:33   ` Thomas Petazzoni via buildroot
2023-09-10 21:32     ` Peter Korsgaard
2023-07-26 20:28 ` [Buildroot] [PATCH v1 3/3] boot/uboot: add host-python-pylibfdt dependency if needed Christian Stewart via buildroot
2023-07-26 20:34   ` Thomas Petazzoni via buildroot
2023-07-26 20:42     ` Christian Stewart via buildroot
2023-07-31 14:10   ` Giulio Benetti
2023-07-31 14:43     ` Thomas Petazzoni via buildroot [this message]
2023-07-31 14:56       ` Christian Stewart via buildroot
2023-07-31 15:02         ` Giulio Benetti
2023-08-06 11:34   ` Thomas Petazzoni via buildroot
2023-09-10 21:33     ` Peter Korsgaard
2023-08-06  7:05 ` [Buildroot] [PATCH v1 1/3] package/python-pylibfdt: bump version to 1.7.0.post1 Sergey Matyukevich
2023-08-06 11:08 ` Lothar Felten
2023-08-06 11:32 ` Thomas Petazzoni via buildroot

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=20230731164321.615664d5@windsurf \
    --to=buildroot@buildroot.org \
    --cc=christian@aperture.us \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.