The correct way to solve this is probably to stop checking in the
generated configure and generate it with a "blessed" autoconf version in
the release tarballs.
On Sun, Sep 11, 2016, at 13:17, Xavier de Gaye wrote:
> On 07/22/2016 06:41 PM, Brett Cannon wrote:
> >
> >
> > On Fri, 22 Jul 2016 at
On Sep 11, 2016, at 16:17, Xavier de Gaye wrote:
> Changeset 816ae3abd928 regenerated the configure script with 'runstatedir'
> again. AFAIK Autoconf 2.70 has still not yet been released. Please let us
> stick
> with 2.69.
As far as I can tell, the spurious "runstatedir" doesn't affect Python bu
On 07/22/2016 06:41 PM, Brett Cannon wrote:
>
>
> On Fri, 22 Jul 2016 at 06:02 Xavier de Gaye mailto:xdeg...@gmail.com>> wrote:
>
> It seems that the configure file on the default branch has been generated
with
> autoconf 2.70. Autoconf 2.70 has not yet been released [1]. The
difference
