mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] at91bootstrap2: make targetinstall v4.x compatible
Date: Tue,  2 May 2023 09:05:53 +0200	[thread overview]
Message-ID: <20230502070553.315410-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20230417115146.745019-1-a.fatoum@pengutronix.de>

Thanks, applied as f1a5e7f131c308d613e6aaf00d07a117c0c03ee9.

Michael

[sent from post-receive hook]

On Tue, 02 May 2023 09:05:53 +0200, Ahmad Fatoum <a.fatoum@pengutronix.de> wrote:
> The binaries directory, where artifacts were previously written to is
> now beneath build/ by default[1]:
> 
>   BUILDDIR ?= ./build
>   BINDIR:=$(BUILDDIR)/binaries
> 
> Supply BUILDDIR=. after the make command to return to the old directory
> scheme. This should have no effect on AT91Bootstrap v3.x and older
> as BUILDDIR was first added in v4.0.0[1].
> 
> [1] https://github.com/linux4sam/at91bootstrap/commit/814f3bdab515287fbb0d972d89d228748613ae91
> 
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> Message-Id: <20230417115146.745019-1-a.fatoum@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/at91bootstrap2.make b/rules/at91bootstrap2.make
> index dcb1157b17f1..c36e30305a92 100644
> --- a/rules/at91bootstrap2.make
> +++ b/rules/at91bootstrap2.make
> @@ -35,7 +35,7 @@ AT91BOOTSTRAP2_WRAPPER_BLACKLIST := \
>  AT91BOOTSTRAP2_MAKE_ENV := \
>  	CROSS_COMPILE=$(BOOTLOADER_CROSS_COMPILE) \
>  	HOSTCC=$(HOSTCC)
> -AT91BOOTSTRAP2_MAKE_OPT := V=$(PTXDIST_VERBOSE)
> +AT91BOOTSTRAP2_MAKE_OPT := V=$(PTXDIST_VERBOSE) BUILDDIR=.
>  
>  ifdef PTXCONF_AT91BOOTSTRAP2
>  $(AT91BOOTSTRAP2_CONFIG):



      parent reply	other threads:[~2023-05-02  7:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-17 11:51 [ptxdist] [PATCH] " Ahmad Fatoum
2023-04-17 11:55 ` Ahmad Fatoum
2023-05-02  7:05 ` Michael Olbrich [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=20230502070553.315410-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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