unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs-diffs Digest, Vol 24, Issue 78
Date: Thu, 11 Nov 2004 21:56:59 +0200	[thread overview]
Message-ID: <01c4c828$Blat.v2.2.2$c05ec5a0@zahav.net.il> (raw)
In-Reply-To: <ED82A851-33B2-11D9-B2C1-000D93505B76@swipnet.se> (jan.h.d@swipnet.se)

> Cc: emacs-devel@gnu.org
> From: "Jan D." <jan.h.d@swipnet.se>
> Date: Thu, 11 Nov 2004 08:25:56 +0100
> 
> > Perhaps some of the recent changes screwed the v1.x build (I last
> > tried to build with v1.x several years ago, and I'm not even sure it
> > will build now), but adding more such problems is hardly the way to
> > treat that ;-)
> 
> No, that is true.  But now there is another problem.  Either v1.x 
> doesn't build because of older changes, or it does not build because of 
> my changes.

It doesn't build because of older changes.  I added to my todo to fix
that one of these days, it simply shouldn't test for djecho for v1.x.
djecho is only required for building Leim, so we should not fail the
whole build if djecho is absent.

As for your change with buildobj.lst, that line in the Makefile will
work with the shell's built-in ECHO commad.  Thus no need to edit
Makefile.in at that point.

> The question is then should v1 be declared unsupported

It _is_ unsupported, since I didn't build with v1.x for a long time.

> (in which case I think config.bat should exit with an appropriate
> message)

I don't want to drop v1.x entirely as long as I don't know for sure
that it cannot be built.

> or the code changed for v1 so Emacs does build?

AFAIK, the v1 version should build.  I'm not aware of any problems
that would prevent that, except for the djecho gork.

  reply	other threads:[~2004-11-11 19:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1CRRTE-0001Bq-Ks@monty-python.gnu.org>
2004-11-10 20:15 ` Emacs-diffs Digest, Vol 24, Issue 78 Eli Zaretskii
2004-11-10 20:44   ` Jan D.
2004-11-10 23:33     ` Eli Zaretskii
2004-11-11  7:25       ` Jan D.
2004-11-11 19:56         ` Eli Zaretskii [this message]
2004-11-12 18:19           ` Eli Zaretskii

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='01c4c828$Blat.v2.2.2$c05ec5a0@zahav.net.il' \
    --to=eliz@gnu.org \
    --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).