unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>, 9459@debbugs.gnu.org
Subject: bug#9459: 24.0.50; Condigure aborts, complains about missing install.sh in build-aux.
Date: Thu, 08 Sep 2011 09:25:37 -0700	[thread overview]
Message-ID: <4E68EC81.5010603@cs.ucla.edu> (raw)
In-Reply-To: <jwvk49jq010.fsf-monnier+emacs@gnu.org>

On 09/07/11 18:46, Stefan Monnier wrote:
> I much prefer a message

I tried that approach, but abandoned it because it didn't work well.
If we do something like this:

         $(srcdir)/configure: $(AUTOCONF_INPUTS)
        -       cd ${srcdir} && autoconf
        +       cd ${srcdir} && autoconf || { \
        +         echo 'Please run ./autogen.sh before reporting a bug.'; \
        +         exit 1; \
        +       }

then the "Please run autogen.sh" message is displayed all the time,
even when autoconf succeeds, because "make" always tells us what it
will do, and the message itself is in the instructions we send to
"make".  I'd rather avoid this sort of annoying chatter in the normal
case.  (The problem can be worked around with some makefile hackery,
but this minor issue isn't worth the complexity.)

> since the failure may be due to too many things.

Yes, of course.  But if the failure is something that autogen.sh can
repair (which was the case with Jan's problem), then invoking
autogen.sh is a win.  And if it's something that autogen.sh can't
repair, then we're no worse off than before.  So falling back on
autogen.sh seems to be a win overall.






  reply	other threads:[~2011-09-08 16:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-07 16:18 bug#9459: 24.0.50; Condigure aborts, complains about missing install.sh in build-aux Jan Djärv
2011-09-07 16:26 ` Glenn Morris
2011-09-07 16:38   ` bug#9459: 24.0.50; Configure " Jan Djärv
2011-09-07 16:44 ` bug#9459: 24.0.50; Condigure " Eli Zaretskii
2011-09-07 18:00   ` Paul Eggert
2011-09-07 18:15   ` Paul Eggert
2011-09-07 18:22     ` Eli Zaretskii
2011-09-07 18:24       ` Lars Magne Ingebrigtsen
2011-09-07 18:39         ` Paul Eggert
2011-09-08  1:46           ` Stefan Monnier
2011-09-08 16:25             ` Paul Eggert [this message]
2011-09-08 16:30               ` Lars Magne Ingebrigtsen
2011-09-08 17:04                 ` Paul Eggert

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=4E68EC81.5010603@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=9459@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    /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).