All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christoph Egger" <Christoph.Egger@amd.com>
To: John Levon <levon@movementarian.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: "portable" sh is not...
Date: Tue, 23 Oct 2007 14:14:38 +0200	[thread overview]
Message-ID: <200710231414.38981.Christoph.Egger@amd.com> (raw)
In-Reply-To: <20071023115443.GA29012@totally.trollied.org.uk>

On Tuesday 23 October 2007 13:54:43 John Levon wrote:
> This commit:
>
> http://xenbits.xensource.com/staging/xen-unstable.hg?rev/08295dc13166
>
> broke our build. The script is not portable as claimed (e.g. traditional
> Bourne shell has no $( ... ) construct).

The only one bash-specific thing I could find was the [:alpha:] notion.
This changeset makes it work on BSD's /bin/sh.
Looks like BSD's /bin/sh is not that traditional... :)

> Christoph, why is this necessary? Surely *BSD have /bin/bash

No, they have not. They have /bin/sh, /bin/ksh and /bin/csh.
bash is a third-party package.

Christoph

-- 
AMD Saxony, Dresden, Germany
Operating System Research Center

Legal Information:
AMD Saxony Limited Liability Company & Co. KG
Sitz (Geschäftsanschrift):
   Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland
Registergericht Dresden: HRA 4896
vertretungsberechtigter Komplementär:
   AMD Saxony LLC (Sitz Wilmington, Delaware, USA)
Geschäftsführer der AMD Saxony LLC:
   Dr. Hans-R. Deppe, Thomas McCoy

  reply	other threads:[~2007-10-23 12:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-23 11:54 "portable" sh is not John Levon
2007-10-23 12:14 ` Christoph Egger [this message]
2007-10-23 12:20   ` John Levon
2007-10-23 12:27     ` Christoph Egger
2007-10-23 12:34       ` John Levon
2007-10-23 12:41         ` Christoph Egger
2007-10-23 13:14           ` John Levon
2007-10-23 13:23             ` Christoph Egger

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=200710231414.38981.Christoph.Egger@amd.com \
    --to=christoph.egger@amd.com \
    --cc=levon@movementarian.org \
    --cc=xen-devel@lists.xensource.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 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.