From: Paul Eggert <eggert@cs.ucla.edu>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: 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 10:04:11 -0700 [thread overview]
Message-ID: <4E68F58B.40304@cs.ucla.edu> (raw)
In-Reply-To: <m3hb4ngfog.fsf@stories.gnus.org>
On 09/08/11 09:30, Lars Magne Ingebrigtsen wrote:
> Can't you put the message in a variable (or something)?
Putting it in a makefile variable won't work, because 'make'
would still expand the variable and display the message
before running autoconf.
We could put the message into a separate shell script (which
we could call "not-autogen.sh" say), but that's overkill.
I can think of other, even fancier ways to attack the problem,
but they're all overkill too.
> or suppress printing this particular line...
But then the user wouldn't be informed when 'autoconf' runs.
We shouldn't do that.
>> > falling back on autogen.sh seems to be a win overall.
> If the build failure is something completely irrelevant to autogen.sh
> (if, for instance, we're hacking the sources)
autogen.sh would be run only when a subset of autogen.sh fails,
so the build failure cannot possibly be irrelevant to autogen.sh.
prev parent reply other threads:[~2011-09-08 17:04 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
2011-09-08 16:30 ` Lars Magne Ingebrigtsen
2011-09-08 17:04 ` Paul Eggert [this message]
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=4E68F58B.40304@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=9459@debbugs.gnu.org \
--cc=larsi@gnus.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.