Re: Broken lisp/Makefile.w32-in

[Juanma Barranquero <lektu@terra.es>]

On Sun, 29 Sep 2002 15:53:47 -0400
"Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> wrote:

> And I don't see anything wrong with requiring such things.
> After all, we also require TeXinfo-4.2, based on the idea that people
> working from the CVS can be expected to have more tools available
> (and more uptodate ones) than people using distribution tarballs.

Yeah, but these requirements aren't documented. Trying to bootstrap
Emacs on a W95 is really painful. I know what I'm doing (or so I think),
and I've never been able to build it by doing:

configure --with-msvc
nmake bootstrap

in a Windows 95. I've needed some cygwin or mingw tools, I've done some
parts of the bootstraping manually, I've had to use 4DOS instead of
COMMAND.COM in some steps of the process (because COMMAND.COM just
wouldn't cut it), but COMMAND.COM in others (because of
incompatibilities of 4DOS.COM), move to the lisp/ directories and
compile the .el files with a "for %i in (*.el)", etc...

OK, as Richard says, most Windows users won't ever bootstrap Emacs.
Perhaps we should abandon the fiction that bootstrapping with
COMMAND.COM is supported, and just say "You're on your own" in the
documentation. I don't know why am I spending time trying to make it
work.

-- 
Juanma Barranquero <lektu@terra.es>