all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Jason Rumney <jasonr@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs can't be built without recent makeinfo
Date: Sat, 03 May 2008 21:58:47 -0400	[thread overview]
Message-ID: <wlr6ciakyw.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <481CDB4D.2070306@gnu.org> (Jason Rumney's message of "Sat, 03 May 2008 22:38:21 +0100")

Jason Rumney wrote:

> It is confusing now, as makeinfo is not needed at all to build a 
> released version of Emacs, but configure aborts if a recent version is 
> not installed.
> Your addition of that test on 2007-08-24 should have instead been an 
> update to the existing test in the maybe_bootstrap rule of Makefile.in. 
> But it looks like you didn't realize that the existing test was there 
> until 2008-01-16, when you removed it.

You're probably right; I'm probably confused.
I'll try and sort it out, but it probably won't be immediate.

This message brought to you by the word "probably". :)




  reply	other threads:[~2008-05-04  1:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-25  4:45 Emacs can't be built without recent makeinfo Nick Roberts
2008-04-25 13:45 ` Stefan Monnier
2008-04-25 16:22   ` Ulrich Mueller
2008-04-25 18:48     ` Glenn Morris
2008-04-25 22:06       ` Nick Roberts
2008-04-25 23:26         ` Glenn Morris
2008-05-03 20:17           ` Glenn Morris
2008-05-03 21:07             ` Jason Rumney
2008-05-03 21:12               ` Glenn Morris
2008-05-03 21:38                 ` Jason Rumney
2008-05-04  1:58                   ` Glenn Morris [this message]
2008-05-04  3:55                 ` Eli Zaretskii
2008-05-05 18:31                   ` Glenn Morris
2008-05-04 21:15             ` Nick Roberts
2008-04-25 22:47 ` Magnus Henoch

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=wlr6ciakyw.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@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 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.