unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: "Denis Bueno" <dbueno@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: CVS HEAD: configure: error: makeinfo >= 4.6 is required on Mac OS X
Date: Sat, 15 Sep 2007 20:22:42 +0200	[thread overview]
Message-ID: <874phv7pql.fsf@ambire.localdomain> (raw)
In-Reply-To: <6dbd4d000709150657y153c71basdbdfcd48a4896f7e@mail.gmail.com> (Denis Bueno's message of "Sat\, 15 Sep 2007 09\:57\:49 -0400")

() "Denis Bueno" <dbueno@gmail.com>
() Sat, 15 Sep 2007 09:57:49 -0400

   For what it's worth, I did what you suggested [1] and it
   still doesn't work.  But if I manually run `makeinfo
   --enable-encoding conftest.texi && echo hi`, "hi" is
   produced as output, so I'm confused.

   Any other suggestions?

i see that you changed configure.in but don't know what else
you did, to be able to say, "it still doesn't work".  here are
some suggestions:

 - w/ those changes, regenerate configure w/ GNU Autoconf 2.61
 - arrange for your system to have a known-good makeinfo
 - rerun configure (a)
 - arrange for your system to have a known-bad makeinfo
 - rerun configure (b)

since the subject of the test is "finding an appropriate
makeinfo", to test thoroughly, we want to see that the result
of (a) is that the makeinfo is found; and that the result of
(b) is that makeinfo is not found and furthermore configure
exits failurefully.

am i missing something?  did you mean something else as "it"?

thi

  reply	other threads:[~2007-09-15 18:22 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
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 [this message]
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=874phv7pql.fsf@ambire.localdomain \
    --to=ttn@gnuvola.org \
    --cc=dbueno@gmail.com \
    --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).