public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: gdb-patches@sourceware.org, brolley@redhat.com, bje@gnu.org,
	        cgen@sources.redhat.com
Subject: Re: RFA: Fix the shell used to execute mloop.in
Date: Tue, 29 Jul 2008 11:50:00 -0000	[thread overview]
Message-ID: <488F03EF.60304@redhat.com> (raw)
In-Reply-To: <y0mabg4e93n.fsf@ton.toronto.redhat.com>

Hi Frank,

>> Oh no, the script is compatible with /bin/sh.  It is just that (if I
>> remember correctly) on some earlier versions of Solaris /bin/sh is
>> broken and you need to use /bin/zsh instead.

I was mistaken - I should have said /bin/ksh not /bin/zsh.

> It would be helpful if you could find some information on this; if
> it's only a rumour, or if it only applies to a fifteen-year-old
> operating system, maybe it's not worth worrying about it.

There are some limitations of various shells mentioned here:

http://www.gnu.org/software/libtool/manual/autoconf/Limitations-of-Builtins.html

Essentially though I think that the correct thing to do is to allow the 
user the choice of which shell they are going to use to execute scripts, 
precisely because of the possibility of bugs in the "standard" shell 
they might exist on their host machine.

Cheers
   Nick

  reply	other threads:[~2008-07-29 11:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-24  7:46 Nick Clifton
2008-07-24 10:15 ` Frank Ch. Eigler
2008-07-24 10:20   ` Nick Clifton
2008-07-24 14:44     ` Frank Ch. Eigler
2008-07-24 15:14       ` Nick Clifton
2008-07-26 19:32         ` Frank Ch. Eigler
2008-07-29 11:50           ` Nick Clifton [this message]
2008-07-29 12:57             ` Frank Ch. Eigler

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=488F03EF.60304@redhat.com \
    --to=nickc@redhat.com \
    --cc=bje@gnu.org \
    --cc=brolley@redhat.com \
    --cc=cgen@sources.redhat.com \
    --cc=fche@redhat.com \
    --cc=gdb-patches@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).