[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bootstrap fails on w32

From: Eli Zaretskii
Subject: Re: Bootstrap fails on w32
Date: Mon, 23 May 2005 06:59:19 +0300

> Date: Mon, 23 May 2005 00:27:19 +0200
> From: Juanma Barranquero <address@hidden>
> Anyway, I agree with David: the files should be in the repository with
> text line endings in the first place, unless there's a real reason not
> to do so.

As Jason pointed out, this would cause trouble to users who build
released Emacs versions from Emacs tarballs.  Please let's not forget
that people who get Emacs via CVS still aren't our main audience...

> And speaking of nt/ oddities: why are the default for DEL/DEL_TREE and
> CP/CP_DIR in nmake.defs so unix-oriented? What's wrong with COPY and
> DEL? OK, there can be an issue with old CMD's compatibility, but
> surely people on Windows 95 with old CMD.EXE/COMMAND.COM is not going
> to have MinGW or Cygwin or GnuWin32 tools installed either... In fact,
> I'd bet there aren't many people building (as opposed to using) Emacs
> on W9X/Me. I'd suggest (for after 22.1, I don't want to cause heart
> strokes to anyone) scrap W95/98/Me *build* compatibility.

Why ``fix'' that which isn't broken?  Emacs still supports platforms
that are much older than Windows 9x, so I certainly don't see any
reasons for such a crusade against W9x build capabilities, nor any
reason to assume that no one builds Emacs on those old versions of

> I ask about the DEL/DEL_TREE/CP/CP_DIR issue because DEL=rm brings me
> trouble in one of my building machines. When bootstraping, the
> lisp/*.elc files are deleted, and calling rm.exe is much, much slower
> than using the internal "del".

Then I'd say get a better port of rm.exe.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]