unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Glenn Morris <rgm@gnu.org>
Cc: Denis Bueno <dbueno@gmail.com>,
	"Emacs Dev \[emacs-devel\]" <emacs-devel@gnu.org>
Subject: Re: CVS HEAD: configure: error: makeinfo >= 4.6 is required on Mac OS X
Date: Fri, 14 Sep 2007 19:57:57 +0200	[thread overview]
Message-ID: <87r6l1t9i2.fsf@ambire.localdomain> (raw)
In-Reply-To: <f7wsutcg69.fsf@fencepost.gnu.org> (Glenn Morris's message of "Fri\, 14 Sep 2007 13\:25\:50 -0400")

here is an excerpt from texinfo 4.6 NEWS:

* Language:
  . new command @/ specifies an allowable breakpoint within a line.
  . new command @dofirstparagraphindent to control whether the first
    paragraph following a section heading is indented.  Default is to
    omit this indentation, unlike the output up to now.
  . new command @indent for explicitly indenting a paragraph.
  . makeinfo writes a new construct for @image in Info output, so that
    graphical Info browsers (such as Emacs Info under X) can display an
    actual image.  (Standalone Info ignores this, since it runs in a tty.)

i see that "grep @indent man/*.texi" yields nine hits.
so how about replacing the version check, like so:

+ echo @indent > conftest.texi
+ if test "$MAKEINFO" != "no" ; then
+    test $MAKEINFO conftest.texi >dev/null 2>&1 || MAKEINFO=no
+ fi
+ rm -f conftest.texi

such a construct is more in line w/ autoconf usage philosophy
(ie, don't check version; check desired features directly).

thi

  reply	other threads:[~2007-09-14 17:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-14 16:37 CVS HEAD: configure: error: makeinfo >= 4.6 is required on Mac OS X Denis Bueno
2007-09-14 17:25 ` Glenn Morris
2007-09-14 17:57   ` Thien-Thi Nguyen [this message]
2007-09-14 19:00     ` Eli Zaretskii
2007-09-14 19:41       ` Thien-Thi Nguyen
2007-09-15 13:57         ` Denis Bueno
2007-09-15 18:22           ` Thien-Thi Nguyen
2007-09-15 19:52             ` Denis Bueno
2007-09-15 19:46         ` Glenn Morris

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=87r6l1t9i2.fsf@ambire.localdomain \
    --to=ttn@gnuvola.org \
    --cc=dbueno@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@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).