Re: compiling groff under uwin using mingw and bash

[michael lindenmeyer]

Ralf:
I decided that the Borland and visual C software was just not working, so went 
back to mingw, and executed configure under using 4 different combinations of 
shell and sed,
ksh and bash, mingw sed and uwin sed. It turned out that the only configures 
that completed with exit 0 were the two run under bash. So, I believe ksh may 
have a problem. Then I found that config.status from the uwin sed hung up on 
the Makefile generation. Running with mingw's sed under bash apparently creates 
a working config.status and an executable Makefile. However, there appears to 
be a problem with a /tmp directory that I don't understand. I am attaching gz 
files for the environment, configure.log, configure.status, Makefile and the 
make process log. From what I observed, I believe that everything is very close 
to working properly, and hope that if I can properly define the /tmp directory, 
that will bring me much closer to compiling groff. I do find the '^M' character 
(it is generated in vi with ctrl v,M) in config.log, but not in config.status 
or Makefile.

Thanks.
Mike
090331.1748

--- On Tue, 3/24/09, Ralf Wildenhues <address@hidden> wrote:

Yes.  It is still the same issue with the added ^M characters that is
bothering configure.

Can you send me (off-list) the
  uwin-base.2007-12-11.win32.i386.exe
  uwin-terminfo.2006-02-14.win32.i386.exe

setmin.gz
Description: GNU Zip compressed data

config.log.gz
Description: GNU Zip compressed data

config.status.gz
Description: GNU Zip compressed data

makefile.gz
Description: GNU Zip compressed data

make.log.gz
Description: GNU Zip compressed data