From: Ladislav Michl <oss-lists@triops.cz>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [EXT] [PATCH] host-dtc: set make env
Date: Wed, 10 Jan 2024 07:40:45 +0100 [thread overview]
Message-ID: <ZZ477cB9n07CFXZq@lenoch> (raw)
In-Reply-To: <15e64b2c1f794f3286baee2b9af3c243@diehl.com>
Hi Denis,
On Mon, Jan 08, 2024 at 02:46:06PM +0100, Denis OSTERLAND-HEIM wrote:
> Hi,
>
> what about using the target parameters here?
> HOST_DTC_MAKE_OPT = $(DTC_MAKE_OPT)
> HOST_DTC_INSTALL_OPT = $(DTC_INSTALL_OPT)
The equality is pure coincidence here, so making them the same could
cause troubes in the future if the need to change one of them arise.
Best regards,
ladis
> Regards, Denis
>
> -----Original Message-----
> From: ptxdist <ptxdist-bounces@pengutronix.de> On Behalf Of Ladislav Michl
> Sent: Friday, January 5, 2024 1:13 PM
> To: ptxdist@pengutronix.de
> Subject: [EXT] [ptxdist] [PATCH] host-dtc: set make env
>
> [EXTERNAL EMAIL]
>
>
> From: Ladislav Michl <ladis@linux-mips.org>
>
> Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
> ---
> rules/host-dtc.make | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/rules/host-dtc.make b/rules/host-dtc.make index
> 586b098bc..e1625ef91 100644
> --- a/rules/host-dtc.make
> +++ b/rules/host-dtc.make
> @@ -28,15 +28,17 @@ HOST_DTC_LICENSE := GPL-2.0-only
> # Prepare
> #
> ----------------------------------------------------------------------------
>
> -HOST_DTC_CONF_TOOL := NO
> -HOST_DTC_MAKE_OPT := \
> +HOST_DTC_CONF_TOOL := NO
> +
> +HOST_DTC_MAKE_ENV := $(HOST_ENV)
> +
> +HOST_DTC_MAKE_OPT := \
> PREFIX=/usr \
> NO_PYTHON=1 \
> NO_VALGRIND=1 \
> - NO_YAML=1 \
> - $(HOST_ENV_CC)
> + NO_YAML=1
>
> -HOST_DTC_INSTALL_OPT := \
> +HOST_DTC_INSTALL_OPT := \
> $(HOST_DTC_MAKE_OPT) \
> install-bin \
> install-lib
> --
> 2.39.2
>
next prev parent reply other threads:[~2024-01-10 6:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 13:46 Denis OSTERLAND-HEIM
2024-01-10 6:40 ` Ladislav Michl [this message]
2024-01-10 7:38 ` Michael Olbrich
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=ZZ477cB9n07CFXZq@lenoch \
--to=oss-lists@triops.cz \
--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