all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
Cc: rich@phekda.freeserve.co.uk
Subject: Re: Emacs CVS & DJGPP CVS: "make bootstrap" fails
Date: Sat, 18 Jan 2003 15:53:56 +0300	[thread overview]
Message-ID: <2110-Sat18Jan2003155356+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <200301181320.h0IDKqDU011701@stubby.bodenonline.com> (jan.h.d@swipnet.se)

> From: "Jan D." <jan.h.d@swipnet.se>
> Date: Sat, 18 Jan 2003 13:25:30 +0100 (MET)
> 
> Yes, I did that.  I checked when HAVE_MENUS gets defined, but it
> did not occur to me that a file in s/ (s/msdos.h) might define it.

Yes, the DJGPP port emulates X menus, see src/msdos.c.  (This
emulation could be the basis of similar support for text terminals on
Unix and GNU systems.)

> I'm guessing DJGPP does not use configure?

Right.  It instead uses config.bat batch file and a bunch of Sed
scripts in the `msdos' subdirectory.

When Emacs 19.2x was ported to DJGPP, there was no Bash port yet, so
running a configure script was not an option.  An additional
disadvantage of using configure, even now, is that one needs lots of
ported packages to be installed, in addition to Bash.  By contrast,
config.bat uses only a small number of widely available ported
programs (Sed, mv, and rm, IIRC), and thus one can build Emacs with
only a minimal set of non-standard tools, which is good for a
fundamental tool such as Emacs, as it avoids a chicken-and-egg problem
to some extent.

      reply	other threads:[~2003-01-18 12:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3E270D14.6DE95026@phekda.freeserve.co.uk>
2003-01-18 10:23 ` Emacs CVS & DJGPP CVS: "make bootstrap" fails Eli Zaretskii
2003-01-18 12:25   ` Jan D.
2003-01-18 12:53     ` Eli Zaretskii [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2110-Sat18Jan2003155356+0200-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=rich@phekda.freeserve.co.uk \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.