Some cygwin/mingw related things
sof at galois.com
Mon Dec 13 13:02:28 EST 2004
The --with-gcc= option isn't understood by the ghc/configure
script -- or any other of the configure scripts kicking around,
I would imagine -- hence ignored.
Save yourself all this bother by putting mingw/bin to the front
of your PATH (it's the right thing to do, anyway), or prefix
a CC setting before invoking the configure script:
foo$ CC=/ming/bin/gcc ./configure <....>
----- Original Message -----
From: "Josef Svenningsson" <josefs at cs.chalmers.se>
To: "Simon Peyton-Jones" <simonpj at microsoft.com>
Cc: "Josef Svenningsson" <josefs at cs.chalmers.se>; "Sigbjorn Finne"
<sof at galois.com>; <cvs-ghc at haskell.org>
Sent: Monday, December 13, 2004 04:47
Subject: RE: Some cygwin/mingw related things
> OK, here's a data point which perhaps will demystify my problems. What I
> did was removing any gcc in my path. Then I configured according to the
> book i.e. --with-gcc=c:/MinGW/bin/gcc . Then configure falls over when it
> tries to configuring ghc. The relevant barfage is like follows:
> configure: configuring in ghc
> configure: running /bin/sh './configure' --prefix=/usr/local
> '--host=i386-unknown-mingw32' '--with-gcc=c:/MinGW/bin/gcc'
> '--enable-src-tree-happy' '--enable-src-tree-alex'
> 'host_alias=i386-unknown-mingw32' --cache-file=/dev/null --srcdir=.
> configure: WARNING: If you wanted to set the --build type, don't
> use --host.
> If a cross compiler is detected then cross compile mode will be used.
> checking for ghc... /cygdrive/c/ghc/ghc-6.2.2/bin//ghc
> checking for i386-unknown-mingw32-gcc... no
> checking for gcc... no
> checking for i386-unknown-mingw32-cc... no
> checking for cc... no
> checking for cc... no
> checking for i386-unknown-mingw32-cl... no
> checking for cl... no
> configure: error: no acceptable C compiler found in $PATH
> See `config.log' for more details.
> configure: error: /bin/sh './configure' failed for ghc
> Now, I don't know the first thing about configure scripts but I hope this
> will give enough info for anyone with a little knowledge to fix the
> problem. I'll be happy to run more experiments and supply more data if
> it's needed.
>> That is strange. If and when you get to the bottom of it, please let me
>> know so that I can update the documentation.
>> I guess Step 1 is to remove cygwin gcc from your path, and see if that
>> helps. If so, the next thing is to find exactly when it's being invoked.
>> (Perhaps by replacing cygwin gcc with a script that barfs)
>> | -----Original Message-----
>> | From: cvs-all-bounces at haskell.org [mailto:cvs-all-bounces at haskell.org]
>> On Behalf Of Josef
>> | Svenningsson
>> | Sent: 10 December 2004 19:36
>> | To: Sigbjorn Finne
>> | Cc: cvs-ghc at haskell.org
>> | Subject: Re: Some cygwin/mingw related things
>> | > Sounds to me as if you've got a cygwin 'gcc' ahead of
>> | > a mingw one in your path, causing you to use the former
>> | > whilst "./configure"ing. If that's the case, play around with
>> | > your PATH setting or use the -with-gcc=<foo> option
>> | > to ./configure.
>> | >
>> | Hmmm. The thing is, I'm already using --with-gcc=<foo> because I know
>> | cygwin gcc comes before the mingw one. I guess I should try fiddle
>> with my
>> | PATH but --with-gcc should do the job shouldn't it?
>> | /Josef
>> | _______________________________________________
>> | Cvs-ghc mailing list
>> | Cvs-ghc at haskell.org
>> | http://www.haskell.org/mailman/listinfo/cvs-ghc
More information about the Cvs-ghc