From: Juanma Barranquero <lektu@terra.es>
Cc: Takaaki.Ota@am.sony.com, emacs-devel@gnu.org
Subject: Re: Broken lisp/Makefile.w32-in
Date: Sat, 31 Aug 2002 20:24:57 -0300 [thread overview]
Message-ID: <20020831175417.49CD.LEKTU@terra.es> (raw)
In-Reply-To: <7263-Fri30Aug2002220645+0300-eliz@is.elta.co.il>
> 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'll try to check it.
> IMHO, if it's feasible to support building on those systems, we should
> do that.
OK.
> Windows 98 SE is still a very popular version of Windows (I,
> for one, prefer it to both Windows/ME and W2K/XP).
Curious. I find both NT 4.0 and W2K to be exceptionally stable (XP is
less so IMHO).
> I think _most_ Windows users download prebuilt binaries, even on W2K
> and Windows/XP.
Well, yes, but supporting building on W2K/XP does not pose any problem
because CMD.EXE is quite more powerful than COMMAND.COM :)
--
Juanma Barranquero <lektu@terra.es>
next prev parent reply other threads:[~2002-08-31 23:24 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 6:59 Broken lisp/Makefile.w32-in Tak Ota
2002-07-31 7:51 ` Juanma Barranquero
2002-08-01 16:52 ` Richard Stallman
2002-08-01 17:14 ` Juanma Barranquero
2002-07-31 8:04 ` Juanma Barranquero
2002-08-30 12:14 ` Juanma Barranquero
2002-08-30 19:06 ` Eli Zaretskii
2002-08-30 23:47 ` Kim F. Storm
2002-08-31 23:24 ` Juanma Barranquero [this message]
2002-09-01 5:11 ` Eli Zaretskii
2002-09-01 21:10 ` Juanma Barranquero
2002-08-31 23:25 ` Juanma Barranquero
2002-09-01 5:15 ` Eli Zaretskii
2002-09-01 19:58 ` Juanma Barranquero
2002-09-01 16:59 ` Eli Zaretskii
2002-09-02 6:18 ` Juanma Barranquero
2002-09-02 16:20 ` Eli Zaretskii
2002-09-04 14:35 ` Juanma Barranquero
2002-09-05 5:08 ` Eli Zaretskii
2002-09-05 6:21 ` Juanma Barranquero
2002-09-05 11:06 ` Andreas Schwab
2002-09-05 14:57 ` Eli Zaretskii
2002-09-05 17:06 ` Juanma Barranquero
2002-09-06 10:47 ` Juanma Barranquero
2002-09-18 6:43 ` Eli Zaretskii
2002-09-20 8:26 ` Juanma Barranquero
2002-09-20 21:23 ` Eli Zaretskii
2002-09-22 17:24 ` Juanma Barranquero
2002-09-22 13:23 ` Eli Zaretskii
2002-09-24 16:46 ` Juanma Barranquero
2002-09-24 18:03 ` Stefan Monnier
2002-09-25 6:36 ` Juanma Barranquero
2002-09-25 14:30 ` Stefan Monnier
2002-09-30 7:02 ` Juanma Barranquero
2002-10-01 6:18 ` Richard Stallman
2002-10-01 14:42 ` Juanma Barranquero
2002-09-29 5:43 ` Juanma Barranquero
2002-09-29 16:38 ` Eli Zaretskii
2002-09-29 19:53 ` Stefan Monnier
2002-09-30 2:06 ` Juanma Barranquero
2002-09-30 1:56 ` Juanma Barranquero
2002-09-30 4:39 ` Eli Zaretskii
2002-09-29 18:44 ` Richard Stallman
2002-10-01 5:58 ` Juanma Barranquero
2002-10-01 13:38 ` Richard Stallman
2002-10-04 7:45 ` Juanma Barranquero
2002-08-30 19:18 ` Richard Stallman
2002-08-31 23:25 ` Juanma Barranquero
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020831175417.49CD.LEKTU@terra.es \
--to=lektu@terra.es \
--cc=Takaaki.Ota@am.sony.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).