public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Christophe Lyon <christophe.lyon@arm.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] genmultilib: Add sanity check
Date: Wed, 2 Nov 2022 18:57:47 +0100	[thread overview]
Message-ID: <5fd04651-5fab-e1d1-ea01-9fc39a1cb207@arm.com> (raw)
In-Reply-To: <3e9c1413-ece9-d28-f02-f04a5f961813@codesourcery.com>



On 11/2/22 18:29, Joseph Myers wrote:
> On Wed, 2 Nov 2022, Christophe Lyon via Gcc-patches wrote:
> 
>> +# Sanity check: make sure we have as many dirnames as options
>> +if [ -n "${dirnames}" ]; then
>> +    options_arr=($options)
> 
> This is an sh script; arrays are a bash feature.  Building GCC isn't
> supposed to need bash (or to rely on $(SHELL) being bash, even when bash
> is available - many GNU/Linux systems use dash for /bin/sh), only a POSIX
> shell.
> 

That's what I feared, and I did "try to try" to build with dash, but I 
realize now that changing SHELL in the generated gcc/Makefile is not 
enough since it's defined by the higher level Makefile/config.status. 
Indeed rebuilding from scratch with CONFIG_SHELL=/bin/dash fails with my 
patch.

We have lived with that behavior for years, so it's not that bad anyway :-)

Thanks,

Christophe

  reply	other threads:[~2022-11-02 17:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 13:10 Christophe Lyon
2022-11-02 17:29 ` Joseph Myers
2022-11-02 17:57   ` Christophe Lyon [this message]
2022-11-03  9:52     ` [PATCH v2] " Christophe Lyon
2022-11-18 19:42       ` Jeff Law
2022-11-21 10:16         ` Mark Wielaard
2022-11-21 12:12           ` Christophe Lyon
2022-11-21 12:32             ` Mark Wielaard
2022-11-21 12:35               ` Christophe Lyon
2022-11-21 23:01                 ` Activate gcc builder problem emails (Was: [PATCH v2] genmultilib: Add sanity check) Mark Wielaard

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=5fd04651-5fab-e1d1-ea01-9fc39a1cb207@arm.com \
    --to=christophe.lyon@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.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 read-only IMAP folder(s) and NNTP newsgroup(s).