Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: David Lawson <david.lawson1@tx.rr.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v3] Makefile: fix use of many br2-external trees
Date: Wed, 21 Sep 2022 20:57:16 +0200	[thread overview]
Message-ID: <20220921185716.GT1419013@scaer> (raw)
In-Reply-To: <2a3ca783-079b-bca6-7fc9-6647b0307eae@mind.be>

Arnout, All,

On 2022-09-21 20:32 +0200, Arnout Vandecappelle spake thusly:
> On 21/09/2022 20:13, Thomas Petazzoni wrote:
> >On Tue, 20 Sep 2022 21:46:45 +0200
> >"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
[--SNIP--]
> >>One of the rationale behind this code, is that we want the defconfig
> >>files from br2-external trees further down the list, to override
> >>defconfig files from those earlier in the list, even overriding the
> >>defconfig files from Buildroot itself.
> >This is the part I would like to challenge. Why do we want to allow
> >BR2_EXTERNAL to override defconfigs from the main tree? We do not allow
> >this for packages, why should we allow it for defconfigs?
>  And indeed, this is exactly the reverse of what we would have now. We have
> two pattern rules that match with the same stem. In this case, according to
> 'info make': "'make' will choose the first one found in the makefile." Since
> we put $(TOPDIR) before the externals in the foreach loop, the internal one
> will be the one that gets used.

As discussed on IRC: except we do not put TOPDIR first; we do:
    $(call reverse,TOPDIR BR2_EXTERNALS)

so the last external does win.

I.e. that patch does not change the current behaviour; it just fixes the
use of more than 5 br2-extenal trees at once.

Sorry, I may not have been clear about the explanations in my commit
log: the rationale part refers to the current code, not the change I
did. Whoever applies it can amend as they see fit, or I can respin if
needed.

Oh, and by the way, I got that privately, so I'll paste it here so that
patchwork catches it:

Tested-by: David Lawson <david.lawson1@tx.rr.com>

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-09-21 18:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20 19:46 [Buildroot] [PATCH v3] Makefile: fix use of many br2-external trees Yann E. MORIN
2022-09-21 18:13 ` Thomas Petazzoni
2022-09-21 18:28   ` Yann E. MORIN
2022-09-21 18:32   ` Arnout Vandecappelle
2022-09-21 18:57     ` Yann E. MORIN [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=20220921185716.GT1419013@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=arnout@mind.be \
    --cc=buildroot@buildroot.org \
    --cc=david.lawson1@tx.rr.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