From: Glenn Morris <rgm@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: /srv/bzr/emacs/trunk r103850: update_autogen
Date: Thu, 07 Apr 2011 12:28:29 -0400 [thread overview]
Message-ID: <pxr59edo0i.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 4D9D45B3.8080502@cs.ucla.edu
Paul Eggert wrote:
> On 04/06/2011 07:18 PM, Glenn Morris wrote:
>
>> Why did you regenerate these with 2.68 (or indeed at all)?
>> Since fencepost has 2.65, they will be reverted the next time my cron
>> job runs.
>
> 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. If suddenly 2.68 is
needed, we should either increase AC_PREREQ, or figure out what recent
change requires 2.68 and remove it.
> 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.
next prev parent reply other threads:[~2011-04-07 16:28 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 [this message]
2011-04-07 18:26 ` Paul Eggert
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=pxr59edo0i.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@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).