configure issue

[Simon Marlow]

On 11/05/2009 10:46, Simon Peyton-Jones wrote:
>
> | -----Original Message-----
> | From: Russel Winder [mailto:russel.winder at concertant.com]
> | Sent: 11 May 2009 10:43
> | To: Simon Marlow; Simon Peyton-Jones
> | Subject: configure issue
> |
> | Simon, Simon,
> |
> | Hopefully soon I will stop making a nuisance of myself :-)
> |
> | I tried reconfiguring and it told me that the development version of GHC
> | is an inappropriate bootstrap.  This seems fine so I pointed it at a
> | 6.10.1 installation I have but:
> |
> |         |>  ./configure --prefix=/opt/GHC-HEAD --with-ghc=/opt/ghc-6.10.1
> |         checking for GHC version date... inferred 6.11.20090509
> |         checking build system type... i686-pc-linux-gnu
> |         checking host system type... i686-pc-linux-gnu
> |         checking target system type... i686-pc-linux-gnu
> |         Canonicalised to: i386-unknown-linux
> |         checking version of ghc... unknown
> |         expr: non-numeric argument
> |         ./configure: line 2922: test: =: unary operator expected
> |         ./configure: line 2941: test: unknownunknown: integer expression expected
> |         ./configure: line 2942: test: unknownunknown: integer expression expected
> |
> | This is a bit worrying ?

I'll fix the message.  You probably set --with-ghc to something that 
isn't actually GHC; perhaps the directory containing GHC?

> |         checking for nhc... no
> |         checking for nhc98... no
> |         checking for hbc... no
> |         checking for ld... /usr/bin/ld
> |         ./configure: line 3346: test: unknown: integer expression expected
> |
> | As is this.

Symptom of same problem.

> |         checking for path to top of build tree... /home/Checkouts/Darcs/GHC
> |         checking whether #! works in shell scripts... yes
> |         checking for perl... /usr/bin/perl
> |         checking if your perl works in shell scripts... yes
> |         checking for python... /usr/bin/python
> |         checking for gcc... gcc
> |         checking for C compiler default output file name... a.out
> |         checking whether the C compiler works... yes
> |         checking whether we are cross compiling... no
> |         checking for suffix of executables...
> |         checking for suffix of object files... o
> |         checking whether we are using the GNU C compiler... yes
> |         checking whether gcc accepts -g... yes
> |         checking for gcc option to accept ISO C89... none needed
> |         checking version of gcc... 4.3.3
> |         checking for extra options to pass gcc when compiling via C...  -fwrapv -
> | mno-omit-leaf-frame-pointer -fno-toplevel-reorder
> |         checking how to run the C preprocessor... gcc -E
> |         checking for a working context diff... diff -U 1
> |         checking for gfind... no
> |         checking for find... /usr/bin/find
> |         checking for sort... /usr/bin/sort
> |         checking for a BSD-compatible install... /usr/bin/install -c
> |         checking for ar... /usr/bin/ar
> |         checking whether /usr/bin/ar is GNU ar... yes
> |         checking for ar arguments... q
> |         checking whether ranlib is needed... no
> |         checking whether /usr/bin/ar supports -input... no
> |         checking whether ln -s works... yes
> |         checking for sed... /bin/sed
> |         checking for time... /usr/bin/time
> |         checking for gtar... no
> |         checking for tar... /bin/tar
> |         checking for gpatch... no
> |         checking for patch... /usr/bin/patch
> |         checking for HsColour... no
> |         checking for xmllint... /usr/bin/xmllint
> |         checking for DocBook DTD... ok
> |         checking for xsltproc... /usr/bin/xsltproc
> |         checking for DocBook XSL stylesheet directory...
> | /usr/share/xml/docbook/stylesheet/nwalsh
> |         checking for fop... /home/users/russel/bin/fop
> |         checking for /home/users/russel/bin/fop usability... yes
> |         checking for xmltex... no
> |         checking for dvips... /usr/bin/dvips
> |         configure: WARNING: cannot find an FO =>  DVI converter, you will not be able
> | to build DVI documentation
> |
> | Is dblatex needed?  Can't it be set up so that any LaTeX installation will do? (I
> | use TeXLive and now dblatex has pulled in TeTex as well :-(
> |
> | (As far as I am aware TeTeX is not maintained; everyone is using TeXLive.)

These are some old tests that aren't necessary any more, I've removed them.

> |         checking for dblatex... no
> |         configure: WARNING: cannot find dblatex in your PATH, you will not be able
> | to build the PDF and PS documentation
> |         checking for ghc-pkg matching /opt/ghc-6.10.1... no
> |         checking for ghc-pkg... /opt/GHC/bin/ghc-pkg
> |
> | This is the development build version that I am about to install over shouldn't it
> | be using the bootstrap install?

Again, the problem is that your --with-ghc wasn't found.

[snip]
> |         ./configure: line 22075: test: argument expected
> |
> | Failures like this are always worrying . . .

What's around line 22075 in your configure script?

Cheers,
	Simon