git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
	 Andy Koppe <andy.koppe@gmail.com>,
	 git@vger.kernel.org,  Patrick Steinhardt <ps@pks.im>
Subject: Re: meson-test syntax error
Date: Thu, 02 Jan 2025 09:27:13 -0800	[thread overview]
Message-ID: <xmqqa5c9unwu.fsf@gitster.g> (raw)
In-Reply-To: <87a5c9uo3n.fsf@igel.home> (Andreas Schwab's message of "Thu, 02 Jan 2025 18:23:08 +0100")

Andreas Schwab <schwab@linux-m68k.org> writes:

> On Jan 02 2025, Junio C Hamano wrote:
>
>> And
>>
>> 	$ make SHELL=/bin/dash test
>>
>> does not seem to pass SHELL=/bin/dash down when it does this part of
>> the Makefile
>>
>>         test: all
>>                 $(MAKE) -C t/ all
>>
>> at the top level.  Oh well.
>
> Command line options (which include macro definitions) are passed
> implicitly to sub makes via the MAKEFLAGS env var.

Yes, that is what I thought.  My complaint was that it didn't seem
to be happening, and it did not cause the bash-ism in check-meson
target to barf.

Thanks.

  reply	other threads:[~2025-01-02 17:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-02 12:17 meson-test syntax error Andy Koppe
2025-01-02 14:25 ` Jonathan Nieder
2025-01-02 14:37   ` Junio C Hamano
2025-01-02 15:22     ` Jonathan Nieder
2025-01-02 15:39       ` Junio C Hamano
2025-01-02 15:41         ` Junio C Hamano
2025-01-02 16:26           ` Junio C Hamano
2025-01-02 17:23             ` Andreas Schwab
2025-01-02 17:27               ` Junio C Hamano [this message]
2025-01-03  6:40         ` Patrick Steinhardt

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=xmqqa5c9unwu.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=andy.koppe@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=ps@pks.im \
    --cc=schwab@linux-m68k.org \
    /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;
as well as URLs for NNTP newsgroup(s).