Mail Archives: djgpp/2002/06/26/04:45:18
Neil Gower <neilg AT inago DOT com> wrote:
> I'm trying to build some code that was distributed with a GNU configure
> script using the MS VC6 compiler (i.e. cl.exe and nmake) on W2K.
[...]
> I set CC=cl, and cl (the compiler) seems to work fine from the prompt.
> However, when I run configure, I get:
[...]
> checking for working autoconf... missing
> checking for working automake... missing
> checking for working autoheader... found
This is rather strange. It's not clear to me how it could have
happened that you can find autoheader, but none of the other auto*
tools.
> checking for gcc... cl
> checking whether the C compiler (cl ) works... no
I rather strongly suspect that the reason for this failure is that MS'
compiler doesn't comply with Unix-ish standards regarding options for
a C compiler --- "why should we?" is MS' typical point of view in
these matters.
In particular, I don't think it ever interpreted option "-ofoo.exe" to
mean "call the generated .exe file foo.exe". It expects
"/out:foo.exe" instead. And that's just the first in a long series of
similar discrepancies.
I guess you will have to provide a wrapper program (Batch file, bash
script, or whatever), that reads a Unix-ish "cc" command line, and
re-writes its arguments into the syntax expected by 'cl'. For further
simplicity, you might just as well call that script 'cc'.
--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -