unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: /srv/bzr/emacs/trunk r103850: update_autogen
Date: Thu, 07 Apr 2011 11:26:07 -0700	[thread overview]
Message-ID: <4D9E01BF.5070306@cs.ucla.edu> (raw)
In-Reply-To: <pxr59edo0i.fsf@fencepost.gnu.org>

On 04/07/2011 09:28 AM, Glenn Morris wrote:

>> Tim Van Holder privately complained to me
>> at Wed, 06 Apr 2011 10:28:12 +0200
>> that the bzr tip didn't build without it.
> 
> I build Emacs just fine with autoconf 2.65, so I'd like to see a bug
> report as to what the problem is supposed to be.

His problem was independent of autoconf versions; it had to do
with the new config.in and configure being needed in order to generate
the proper symbols that the new src/*.c files were using.  He didn't
have a proper autoconf on his platform, and so was relying on the
fallback copies of config.in and configure that are checked in somewhere
else.

>> Would it be a lot of hassle to have the fencepost cron job use
>> Autoconf 2.68?
> 
> No, but I don't see why it should bother if configure.in does not
> require such a version.

Well, for one thing, we'll avoid unnecessary churning due only
to Autoconf version skew.  :-)  If we're going to use some
Autoconf version for the cron job, we might as well use the
latest stable version, since it generates a bit better output.

Again, it's no big deal, as maintainers should be expected to
work around any of these issues.  I do hope, though, that the
latest Autoconf is used whenever we make a tarball intended for
non-maintainers.



  reply	other threads:[~2011-04-07 18:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Q7YEZ-0005TE-HZ@colonialone.fsf.org>
2011-04-07  2:18 ` /srv/bzr/emacs/trunk r103850: update_autogen Glenn Morris
2011-04-07  5:03   ` Paul Eggert
2011-04-07 16:28     ` Glenn Morris
2011-04-07 18:26       ` Paul Eggert [this message]
2011-04-08  0:08         ` Glenn Morris
2011-04-08  2:04           ` Paul Eggert
2011-04-08  4:16             ` Stephen J. Turnbull
2011-04-08  6:47               ` Paul Eggert
2011-04-08 16:09                 ` Chong Yidong
2011-04-09  1:29         ` Stefan Monnier
2011-04-09 17:50           ` 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=4D9E01BF.5070306@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@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).