unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: 17258@debbugs.gnu.org
Subject: bug#17258: autogen.sh doesn't update stale autoconf files in build-aux
Date: Sun, 13 Apr 2014 13:30:43 +0200	[thread overview]
Message-ID: <8761md1n6k.fsf@Rainer.invalid> (raw)
In-Reply-To: <87fvlhio6b.fsf@Rainer.invalid>

[would you please not quote full email addresses?]

Eli Zaretskii writes:
>> My expectation would be that any call to autogen.sh would re-create
>> these files.
>
> That's not enough (assuming we indeed want these files to be
> re-created automatically): just running "make" will invoke the
> autotools as needed.  In fact, after the initial invocation of
> autogen.sh, you should normally never again need to run it by hand.

The Makefile (at least on GNU/Linux) actually calls autotools through
autogen.sh and not directly.  And since that is so, whether or not I
call it by hand or through the Makefile doesn't change the fact that
after an upgrade of autotools on your system or if you've somehow edited
or damaged those files you'll end up with stale files in build-aux that
may or may not work correctly.

It may not be appropriate to unconditionally replace these files each
times autoreconf is run, but there should be at least an option for
autogen.sh to do this.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada






  reply	other threads:[~2014-04-13 11:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-13  9:17 bug#17258: autogen.sh doesn't update stale autoconf files in build-aux Achim Gratz
2014-04-13 10:19 ` Eli Zaretskii
2014-04-13 10:50   ` Achim Gratz
2014-04-13 11:02     ` Eli Zaretskii
2014-04-13 11:30       ` Achim Gratz [this message]
2014-04-13 11:39         ` Eli Zaretskii
2014-04-14  5:45 ` Paul Eggert
2014-04-14 17:14   ` Achim Gratz

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=8761md1n6k.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=17258@debbugs.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).