all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>, 9459@debbugs.gnu.org
Subject: bug#9459: 24.0.50; Condigure aborts, complains about missing install.sh in build-aux.
Date: Wed, 07 Sep 2011 20:24:47 +0200	[thread overview]
Message-ID: <m3k49kp5w0.fsf@stories.gnus.org> (raw)
In-Reply-To: <83aaag6wm9.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 07 Sep 2011 21:22:22 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> My opinion: no, please don't.  Such changes are rare enough and far in
> between, while normal builds are much more frequent.  It only takes
> one botched build to learn to run autogen.sh manually when "make"
> won't cut it.

I agree.

But would it be possible to have "make" spit out "Compilation failed;
have you tried running ./autogen.sh before reporting this as a bug?" if
building fails?  :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/





  reply	other threads:[~2011-09-07 18:24 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 [this message]
2011-09-07 18:39         ` Paul Eggert
2011-09-08  1:46           ` Stefan Monnier
2011-09-08 16:25             ` Paul Eggert
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3k49kp5w0.fsf@stories.gnus.org \
    --to=larsi@gnus.org \
    --cc=9459@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.