Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Kristof Havasi <havasiefr@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] Build regression after 2022.02.01
Date: Thu, 28 Apr 2022 23:22:37 +0200	[thread overview]
Message-ID: <20220428232237.602ccb13@windsurf> (raw)
In-Reply-To: <CADBnMvhgaozAgZgy3njckjL1i0U6bZ0fLrq-kdFF-qpGhFWgmw@mail.gmail.com>

Hello Kristof,

On Thu, 28 Apr 2022 19:39:11 +0200
Kristof Havasi <havasiefr@gmail.com> wrote:

> I just updated from 2022.02 to 2022.02.01.
> 
> My build broke due to 8945ba49480a7885d10444
> "toolchain/toolchain-external: error if BR2_TOOLCHAIN_EXTERNAL_PATH is not set"
> 
> I selected a bootlin toolchain for armv7, which is installed on the
> build system and is available
> via PATH. As the help string of BR2_TOOLCHAIN_EXTERNAL_PATH describes, if it is
> empty, then PATH will be searched.
> 
> If I revert the above commit the build succeeds like before.
> 
> I could see the reason behind the check in the commit for the case,
> where the toolchain is yet to be downloaded, but then the lines ended
> up in the wrong
> branch of the if/else statement.
> 
> In case the toolchain is already available via PATH, I suggest to
> follow the previous logic
> and description in the help text:
>      "If empty, the compiler will be searched in $PATH."

Thanks for your report. I believe that commit 8945ba49480a7885d10444 is
incorrect, so I sent a patch to propose to revert it:

  https://patchwork.ozlabs.org/project/buildroot/patch/20220428212011.534725-1-thomas.petazzoni@bootlin.com/

Let's see the feedback from the original author and the other Buildroot
maintainers who applied. Maybe I missed something, but my belief is
that the patch is incorrect.

Again, thanks for your report, much appreciated!

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:[~2022-04-28 21:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28 17:39 [Buildroot] Build regression after 2022.02.01 Kristof Havasi
2022-04-28 21:22 ` Thomas Petazzoni via buildroot [this message]

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=20220428232237.602ccb13@windsurf \
    --to=buildroot@buildroot.org \
    --cc=havasiefr@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