mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Ladislav Michl <oss-lists@triops.cz>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 1/3] rules: Remove default assignments to <PKG>_PATH and <PKG>_ENV
Date: Tue, 18 Oct 2022 10:16:34 +0200	[thread overview]
Message-ID: <Y05g4qx7e8njA0eN@lenoch> (raw)
In-Reply-To: <Y05aUkZd2iD+8Mwv@pengutronix.de>

On Tue, Oct 18, 2022 at 09:48:34AM +0200, Michael Olbrich wrote:
> On Mon, Oct 17, 2022 at 09:59:04PM +0200, Ladislav Michl wrote:
> > From: Ladislav Michl <ladis@linux-mips.org>
> > 
> > Undefined <PKG>_PATH is set to PATH=$(CROSS_PATH) for target packages,
> > PATH=$(HOST_PATH) for host packages and PATH=$(HOST_CROSS_PATH) for
> > cross packages.
> > 
> > Undefined <PKG>_ENV is set to $(CROSS_ENV) for target packages,
> > $(HOST_ENV) for host packages and $(HOST_CROSS_ENV) for cross
> > packages.
> 
> Hmmm, <PKG>_ENV is also used in the install stage and it has no default
> here. But it's not used in the compile stage. In general I think those two
> stages should have the default environment. So if this breaks something,
> then it was probably somewhat broken anyways.
> I'll throw in in my 'build everything' test. Let's see what happens here.

Thank you,

it was meant as preparation for <PKG>_AUTOCONF removal patch where
<PKG>_CONF_ENV is used when needed. <PKG>_AUTOCONF and <PKG>_ENV 
are two heavily used deprecated variables. There are few <PKG>_MAKEVARS
and <PKG>_COMPILE_ENV left.

I can prepare patch to replace them, so we can bail out with error after
some transitional period.

	l.

> Michael




  reply	other threads:[~2022-10-18  8:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17 19:57 [ptxdist] [PATCH 0/3] Cleanup autoconf rules Ladislav Michl
2022-10-17 19:59 ` [ptxdist] [PATCH 1/3] rules: Remove default assignments to <PKG>_PATH and <PKG>_ENV Ladislav Michl
2022-10-18  7:48   ` Michael Olbrich
2022-10-18  8:16     ` Ladislav Michl [this message]
2022-10-28 14:44   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-10-17 19:59 ` [ptxdist] [PATCH 2/3] rules: Replace deprecated <PKG>_AUTOCONF Ladislav Michl
2022-10-18  9:20   ` [ptxdist] [PATCH v2] " Ladislav Michl
2022-10-18 20:08     ` [ptxdist] [PATCH v3] " Ladislav Michl
2022-10-28 14:44       ` [ptxdist] [APPLIED] " Michael Olbrich
2022-10-17 19:59 ` [ptxdist] [PATCH 3/3] bsdiff: Fix configuration tool (not) used Ladislav Michl
2022-10-28 14:44   ` [ptxdist] [APPLIED] " 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=Y05g4qx7e8njA0eN@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