[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Groff] Re: MSVC Port
From: |
Werner LEMBERG |
Subject: |
Re: [Groff] Re: MSVC Port |
Date: |
Fri, 28 Nov 2003 12:13:53 +0100 (CET) |
> > What exactly do you mean with 1.19.2? The latest release is 1.19,
> > and I assume that 1.19.1 identifies the curren CVS, right?
>
> Read twice, send once ...
Your reply is probably something witty, unfortunately I don't
understand it...
> My diff has the c option but not the u option.
This is fine also.
> > Another fix is to set ac_executable_extensions to ".exe" (or
> > ".exe .cmd .bat" if you like) in your config.site. That
> > variable was added for this exact purpose - not all Unixy shells
> > on DOS/Windows return true for 'test -x foo' if only foo.exe
> > exists.
> >
> > This is an undocumented feature of autoconf:
>
> Documenting it would help ... However, even with this set, the test
> fails. configure finds cc (MKS front end to MSVC), but tries to run
> b.out.
I'll forward your results to the bug-autoconf list.
> > My suggestion was to have a small predefined list of extensions
> > (just ".exe", to be precise) to try if the compiler name without
> > extensions doesn't work. Let's see how (and when) the autoconf
> > people will fix that.
>
> Seems reasonable enough, but it also should be simple enough to
> discover the proper extension.
What exactly do you mean?
> > Just curious: If you say `CC=cl.exe' and `CXX=cl.exe' does it then
> > work without a configure script patch related to EXEEXT?
>
> Yes, as does CC=cl and CXX=cl--for now this would seem the most
> expedient workaround.
So it seems the problem is the `cc' MKS front end. Another
experiment: Have you tried to move `cc' temporarily out of PATH so
that autoconf finds `cl'? Does it work then?
Werner
Message not available