Re: config.status problem with UWIN

[Ralf Wildenhues]

Hello Werner,

* Werner LEMBERG wrote on Mon, Mar 09, 2009 at 02:37:44PM CET:
> please have a look at the two config.status files.  One has been
> created on my GNU/Linux box, the other one on MS-Windows:
> 
>   uname -m = i1586
>   uname -r = 4.2/5.1
>   uname -s = UWIN-XP
>   uname -v = 2600
> 
> while the configure script runs successfully on both boxes, executing
> config.status creates only empty files on the Windows box (at least
> the top-level Makefile is empty).  This looks like a bug.  I notice
> that many regexps which replace @...@ with proper values contain
> additional `^M' bytes.  This can't be correct, I think.

I agree.  Can you retry with current git Autoconf (i.e., build and
install that somewhere, and run its autoreconf -vif on groff)?

If it doesn't work either, then I guess it would be interesting to see
  sh -x ./configure

output for a small example configure script, say, the one corresponding
to this configure.ac file:
  AC_INIT([pkg], [1], [devnull])
  AC_CONFIG_FILES([file])
  AC_OUTPUT

and an empty file.in.

I've only ever w32-tried the newer config.status stuff (which uses awk
for substitutions) with Cygwin and MinGW and in cross compiles from
GNU/Linux.  IIRC Interix should work, but I don't remember any UWIN
feedback.  Seems I might have to install that sometimes.  Which UWIN
packages do I need to reproduce this?

Thanks for the report,

Cheers,
Ralf