On 2005-03-16 16:14+0100 Arjen Markus wrote:
> Hello all,
> I tried to run ./configure on Windows XP in the MingW environment,
> and while the script itself runs smoothly, it arrives at a rather
> unfavourable conclusion:
> $ CC=cl.exe
> $ ./configure
> checking for a BSD-compatible install... /bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking for gcc... no
> checking for cc... no
> checking for cc... no
> checking for cl... cl
> checking for C compiler default output file name... configure: error: C
> compiler cannot create executables
> See `config.log' for more details.
> Needless to say that "config.log" does not hold any details about the
> particular problem
> I need to solve now :(
> Apparently, ./configure requires a single-step compile/link process. I
> can build a small script that
> will do this, but it is a bit of a disappointment.
> Just to keep you all informed about it!
Arjen, does the following overview describe what you are trying to do?
As I understand it, mingw consists of a minimal GNU environment including
bash shell, make, and gcc compiler set that works fairly well for Andrew
Roach on windows. So are you trying to use the mingw shell and make, but
substitute the windows visual C++ tools for the gcc compiler collection?
If so, just to confirm you have everything working properly for normal mingw
with the gcc compiler collection, you may first want to follow Andrew's
mingw instructions in INSTALL.
Once say the postscript device driver works for you under normal mingw with
gcc, then Chapter 2.6 (which I quoted before) of the autotools book seems to
indicate that if you substitute the visual C++ tools for the gcc compiler
collection, everything should continue to work subject to dealing with
cross-platform issues that might show up.
For example, the above configure output seems to indicate the visual C++
compiler (cl) was found, but it has some limitations that have to be worked
around. google seems to be down at the moment, but I would look for that
error message there to see if there is an obvious solution that does not
require scripting on your part. Also, note that scripting on your part may
not be a good workaround; libtool logic which may have certain things it
tries to do for the case when CC=cl.exe.
Alan W. Irwin
Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).
Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the Yorick front-end to PLplot (yplot.sf.net); the
Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project