unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Ulrich Mueller <ulm@gentoo.org>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-devel@gnu.org
Subject: Re: Emacs can't be built without recent makeinfo
Date: Fri, 25 Apr 2008 19:26:07 -0400	[thread overview]
Message-ID: <b6ve25v7n4.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <18450.21976.563496.841851@kahikatea.snap.net.nz> (Nick Roberts's message of "Sat, 26 Apr 2008 10:06:16 +1200")

Nick Roberts wrote:

> Clearly it's not a _big_ issue as no-one else has reported a problem
> but it seems logical to me that if texinfo is missing/too old then
> Emacs just gets built without the manuals and this is reported at
> configure time.

How about doing the same kind of thing as is now done with X and image
libraries: by default configure aborts if these are missing, but you
can pass an option to indicate you want to build without them.

These are features that almost everyone wants, and having configure
just print a message that they are missing was often overlooked.




  reply	other threads:[~2008-04-25 23:26 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 [this message]
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=b6ve25v7n4.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=nickrob@snap.net.nz \
    --cc=ulm@gentoo.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).