Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Arnout Vandecappelle via buildroot <buildroot@buildroot.org>
Cc: James Hilliard <james.hilliard1@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/pkg-generic.mk: fix rule order for re{install, build, configure}
Date: Fri, 13 Oct 2023 16:41:48 +0200	[thread overview]
Message-ID: <87o7h24mab.fsf@48ers.dk> (raw)
In-Reply-To: <dfe9844e-5208-4d19-3af9-0faf8c0a5abf@mind.be> (Arnout Vandecappelle via buildroot's message of "Sun, 1 Oct 2023 18:05:19 +0200")

>>>>> "Arnout" == Arnout Vandecappelle via buildroot <buildroot@buildroot.org> writes:

 >  Hi James,
 > On 18/10/2022 05:46, James Hilliard wrote:
 >> These command rely on the clean operations being first so that the
 >> stamp files being deleted will rebuild the targets.
 >> The execution ordering of the clean and rebuild operations may
 >> change, for example if --shuffle=reversed is set.
 >> To ensure the evaluation order is always correct use double colon
 >> rules to make the evaluation order explicit as per make docs:
 >> The double-colon rules for a target are executed in the order they
 >> appear in the makefile.

 >  As noted in earlier discussions, this feels a bit hackish and it's
 >  not clear if this behaviour is going to be kept in future versions of
 > make.

 >  Since make 4.4, however, there's a better solution: it introduced a
 >  .WAIT phony target that enforces the ordering of dependencies. So I
 > instead made a commit[1] that uses that approach.

Committed to 2023.02.x and 2023.08.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-10-13 14:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18  3:46 [Buildroot] [PATCH 1/1] package/pkg-generic.mk: fix rule order for re{install, build, configure} James Hilliard
2023-01-09 22:07 ` Charles Hardin
2023-02-12  9:42 ` Yann E. MORIN
2023-02-12 10:02   ` James Hilliard
2023-02-12 10:11     ` Yann E. MORIN
2023-02-12 10:22       ` James Hilliard
2023-02-12 10:57         ` Yann E. MORIN
2023-02-12 11:17           ` James Hilliard
2023-02-14 21:22   ` Arnout Vandecappelle
2023-02-14 21:24     ` Arnout Vandecappelle
2023-07-13 22:33       ` James Hilliard
2023-10-01 16:05 ` Arnout Vandecappelle via buildroot
2023-10-13 14:41   ` Peter Korsgaard [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=87o7h24mab.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=james.hilliard1@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