unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Nick Roberts <nickrob@snap.net.nz>, emacs-devel@gnu.org
Subject: Re: Emacs can't be built without recent makeinfo
Date: Fri, 25 Apr 2008 18:22:30 +0200	[thread overview]
Message-ID: <18450.1350.18815.221139@a1ihome1.kph.uni-mainz.de> (raw)
In-Reply-To: <jwvlk32oxpb.fsf-monnier+emacs@gnu.org>

>>>>> On Fri, 25 Apr 2008, Stefan Monnier wrote:

>>> From configure:
>> if test "$MAKEINFO" = "no"; then
>> { { echo "$as_me:$LINENO: error: makeinfo >= 4.6 is required " >&5
>> echo "$as_me: error: makeinfo >= 4.6 is required " >&2;}
>> { (exit 1); exit 1; }; }
>> fi

>> Do we really want to stop the build process completely just because the online
>> manuals can't be properly built?

> Indeed, no.  Especially since they are supposed to be pre-built in
> the tarball.  The test should/could be moved to the Makefile, maybe?

Is this really an issue? texinfo 4.6 was released in 2003.

<http://www.gnu.org/software/texinfo/> lists it under "Very old
releases, for historical and archeological purposes." :-)

Ulrich




  reply	other threads:[~2008-04-25 16:22 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 [this message]
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
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

  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=18450.1350.18815.221139@a1ihome1.kph.uni-mainz.de \
    --to=ulm@gentoo.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=nickrob@snap.net.nz \
    /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).