[Top][All Lists]

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

Re: Broken lisp/Makefile.w32-in

From: Eli Zaretskii
Subject: Re: Broken lisp/Makefile.w32-in
Date: Fri, 30 Aug 2002 22:06:45 +0300

> From: Juanma Barranquero <address@hidden>
> Date: Fri, 30 Aug 2002 14:14:19 +0200
> >     echo (normal-top-level-add-to-load-path $(SQUOTE)(>> subdirs.el
> >     @for %d in ($(WINS)) do if not (%d)==(term) echo "%d">> subdirs.el
> >     echo ))>> subdirs.el
> Before commiting this code to lisp/makefile.w32-in, "nmake
> update-subdirs" didn't work in any Windows target that I tried. With it,
> updating subdirs works in modern Windows, but still fails on W95 with
> COMMAND.COM (the "for" somehow manages to send just one directory to
> subdirs.el).

Can you figure out why is that failing?  Could it be that $WINS is so
long that the resulting command exceeds the 126-character limit on
COMMAND.COM's command line, for example?

> I'm not sure about W98 and Me, although I'd love to know.

They both use COMMAND.COM, so the same problems should show up.

> There's no question that the Windows port should continue supporting
> *running* in old W95 and W98 machines, but it is really worthwhile to
> continue supporting *building* on those machines?

IMHO, if it's feasible to support building on those systems, we should
do that.  Windows 98 SE is still a very popular version of Windows (I,
for one, prefer it to both Windows/ME and W2K/XP).

> I'd bet Emacs users on W95/98 do use binary tarballs and don't build
> their own Emacs.

I think _most_ Windows users download prebuilt binaries, even on W2K
and Windows/XP.

reply via email to

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