From: Thomas Huth <thuth@redhat.com>
To: Richard Zak <richard.j.zak@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: Eric Blake <eblake@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH 2/2] Fix for Haiku
Date: Sun, 4 Jul 2021 09:16:52 +0200 [thread overview]
Message-ID: <557b3546-d263-cfd0-3e49-a1a00eb61b93@redhat.com> (raw)
In-Reply-To: <CAOakUfOz=89WuCyAQhrebNj_K_3_2ZYAJ_=aRR2bAuKT5=9uow@mail.gmail.com>
On 03/07/2021 23.12, Richard Zak wrote:
> Fix for path to env
Please change the subject to something more meaning full, e.g. "Fix setting
of the SHELL variable for Haiku".
In the patch description, you should mention that there is no /usr/bin/env
on Haiku.
> Signed-off-by: Richard Zak <richard.j.zak@gmail.com
> <mailto:richard.j.zak@gmail.com>>
> ---
> Makefile | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Makefile b/Makefile
> index 30f19d33bb..ced9b97372 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -14,7 +14,11 @@ SRC_PATH=.
> # we have explicit rules for everything
> MAKEFLAGS += -rR
>
> +ifneq ($(BE_HOST_CPU),)
> +SHELL = /bin/env bash -o pipefail
> +else
> SHELL = /usr/bin/env bash -o pipefail
> +endif
Actually, I wonder why we had to take the detour via /usr/bin/env here at
all? Couldn't we simply set
SHELL = bash -o pipefail
by default, or does this cause some trouble on other systems?
If nobody objects, I'd suggest that you change your patch to always set
"SHELL = bash -o pipefail" unconditionally.
Thomas
next prev parent reply other threads:[~2021-07-04 7:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-03 21:12 [PATCH 2/2] Fix for Haiku Richard Zak
2021-07-04 7:16 ` Thomas Huth [this message]
2021-07-04 10:00 ` Philippe Mathieu-Daudé
2021-07-04 13:51 ` Philippe Mathieu-Daudé
2021-07-04 14:26 ` Richard Zak
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=557b3546-d263-cfd0-3e49-a1a00eb61b93@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.j.zak@gmail.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;
as well as URLs for NNTP newsgroup(s).