Re: [patch] Do not call bash but sh in the "boot" script

2010-04-11 Thread Matthias Kilian
On Mon, Apr 12, 2010 at 11:47:26AM +1000, Ben Lippmeier wrote: > The trouble is that the boot scripts use GNU specific features. > I was the one that changed it to bash because I was tired of the > build breaking on Solaris. I think the original problem was that > the Solaris version of 'test' does

[nightly] 11-Apr-2010 build of STABLE on i386-unknown-linux (cam-02-unx.europe.corp.microsoft.com)

2010-04-11 Thread GHC Build Reports
Build description = STABLE on i386-unknown-linux (cam-02-unx.europe.corp.microsoft.com) Build location= /playpen/simonmar/nightly/STABLE Build config file = /home/simonmar/nightly/site/msrc/conf-STABLE-cam-02-unx Nightly build started on cam-02-unx at Sun Apr 11 18:10:01 BST 2010. checki

Re: [patch] Do not call bash but sh in the "boot" script

2010-04-11 Thread Lars Viklund
The core problem from a FreeBSD viewpoint is that the base system does not contain bash. Unlike most OSes out there, the base system is really basic, having no vim, perl, etc. If you want it, you need to install it yourself from either a package or ports. The shells that are in base are as far as

pgj, build 4, Failure

2010-04-11 Thread Builder
pgj, build 4 Build failed Details: http://darcs.haskell.org/ghcBuilder/builders/pgj/4.html darcs checkout | Success create mk/build.mk | Success get subrepos | Success repo versions| Success setting version date | Success booting | Success configuring

pgj2, build 4, Failure

2010-04-11 Thread Builder
pgj2, build 4 Build failed Details: http://darcs.haskell.org/ghcBuilder/builders/pgj2/4.html darcs checkout | Success create mk/build.mk | Success get subrepos | Success repo versions| Success setting version date | Success booting | Success configuring

Re: [patch] Do not call bash but sh in the "boot" script

2010-04-11 Thread Ben Lippmeier
The trouble is that the boot scripts use GNU specific features. I was the one that changed it to bash because I was tired of the build breaking on Solaris. I think the original problem was that the Solaris version of 'test' doesn't support some of the flags being used, but I'm sure there are ot

[nightly] 11-Apr-2010 build of STABLE on x86_64-unknown-linux (cam-04-unx.europe.corp.microsoft.com)

2010-04-11 Thread GHC Build Reports
Build description = STABLE on x86_64-unknown-linux (cam-04-unx.europe.corp.microsoft.com) Build location= /64playpen/simonmar/nightly/STABLE-cam-04-unx Build config file = /home/simonmar/nightly/site/msrc/conf-STABLE-cam-04-unx Nightly build started on cam-04-unx at Sun Apr 11 19:10:01 BST 20

[nightly] 11-Apr-2010 build of HEAD on x86_64-unknown-linux (cam-04-unx.europe.corp.microsoft.com)

2010-04-11 Thread GHC Build Reports
Build description = HEAD on x86_64-unknown-linux (cam-04-unx.europe.corp.microsoft.com) Build location= /64playpen/simonmar/nightly/HEAD-cam-04-unx Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-04-unx Nightly build started on cam-04-unx at Sun Apr 11 19:00:01 BST 2010. **

[nightly] 11-Apr-2010 build of HEAD on i386-unknown-linux (cam-02-unx.europe.corp.microsoft.com)

2010-04-11 Thread GHC Build Reports
Build description = HEAD on i386-unknown-linux (cam-02-unx.europe.corp.microsoft.com) Build location= /playpen/simonmar/nightly/HEAD Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-02-unx Nightly build started on cam-02-unx at Sun Apr 11 18:00:01 BST 2010. checking out

[patch] Do not call bash but sh in the "boot" script

2010-04-11 Thread Gabor PALI
Hello, While working with the latest GHC sources on FreeBSD, I found that the "boot" script calls bash without any reason. In that script, bash is used for running "boot-pkgs" which has a shebang line referring to sh only (i.e. it is not a bash script). In my opinion, bash should be omitted for

pgj2, build 3, Failure

2010-04-11 Thread Builder
pgj2, build 3 Build failed Details: http://darcs.haskell.org/ghcBuilder/builders/pgj2/3.html darcs checkout | Success create mk/build.mk | Success get subrepos | Success repo versions| Success setting version date | Success booting | Success configuring