All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: Ben Taylor <sol10x86@cox.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Patch to make configure /bin/sh compatible
Date: Fri, 14 Apr 2006 18:57:17 +0100	[thread overview]
Message-ID: <20060414175717.GH4696@networkno.de> (raw)
In-Reply-To: <20060414174346.ZGFE14554.eastrmmtao03.cox.net@[172.18.52.8]>

Ben Taylor wrote:
> Thiemo Seufer <ths@networkno.de>
> > 
> > Ben Taylor wrote:
> > > This is a patch to make configure truly /bin/sh compatible,
> > > as well as changing some logic to remove "echo -n" for
> > > output to files, as "echo -n" is not consistent among
> > > environments.
> > > 
> > > This is against the latest cvs branch, and I appreciate
> > > any feedback.
> > 
> > [snip]
> > > @@ -294,7 +295,7 @@
> > >          target_list="i386-user arm-user armeb-user sparc-user ppc-user mips-user mipsel-user $target_list"
> > >      fi
> > >  else
> > > -    target_list=$(echo "$target_list" | sed -e 's/,/ /g')
> > > +    target_list=`echo "$target_list" | sed -e 's/,/ /g'`
> > 
> > A standard-conforming /bin/sh should be capable of handling this.
> 
> do you mean a shell that looks like /bin/sh but is really
> more like ksh or bash.  Solaris /bin/sh did not like
> that construct.

I meant
http://www.opengroup.org/onlinepubs/007908799/xcu/chap2.html#tag_001_006_003
which IIRC looks that way since POSIX times.

Apparently Solaris isn't conformant WRT.


Thiemo

  reply	other threads:[~2006-04-14 17:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-14 17:43 Re: [Qemu-devel] Patch to make configure /bin/sh compatible Ben Taylor
2006-04-14 17:57 ` Thiemo Seufer [this message]
     [not found] <BAY0-MC6-F17UW5RmrG0011a6d8@bay0-mc6-f17.bay0.hotmail.com>
2006-04-20 15:08 ` Nathan Kunkee
  -- strict thread matches above, loose matches on Subject: below --
2006-04-14 15:57 Ben Taylor
2006-04-14 17:22 ` Thiemo Seufer
2006-04-14 17:38   ` Michael McConnell
2006-04-14 17:39   ` Anderson Lizardo

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=20060414175717.GH4696@networkno.de \
    --to=ths@networkno.de \
    --cc=qemu-devel@nongnu.org \
    --cc=sol10x86@cox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.