From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Christoph Egger" Subject: Re: getting etherboot compiling Date: Mon, 4 Feb 2008 17:18:52 +0100 Message-ID: <200802041718.52943.Christoph.Egger@amd.com> References: <20080201181647.GA7841@totally.trollied.org.uk> <200802041124.06583.Christoph.Egger@amd.com> <18343.13528.850110.443359@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <18343.13528.850110.443359@mariner.uk.xensource.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Jackson Cc: xen-devel@lists.xensource.com, John Levon List-Id: xen-devel@lists.xenproject.org On Monday 04 February 2008 16:52:56 Ian Jackson wrote: > Christoph Egger writes ("Re: [Xen-devel] getting etherboot compiling"): > > This is not ok for *BSD. bash is a third-party package there. > > I think this is OK in a tool needed for building, surely ? After all > you need GCC to build Xen and that's a third-party package in *BSD > too. GCC is in the base system. Install a BSD and have a look. > However, it's a very simple script and I can't see anything in it > which ought not to work (ie, I think it uses only features in SuSv3). > What is the problem that means Solaris /bin/sh doesn't work ? Neither do I. It works with *BSD's /bin/sh. However, Solaris /bin/sh is a much older bourne shell than on BSD. Christoph