[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: how to detect int64?

From: Eric Blake
Subject: Re: how to detect int64?
Date: Mon, 19 Jul 2010 15:43:01 -0600
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100621 Fedora/3.0.5-1.fc13 Lightning/1.0b2pre Mnenhy/0.8.3 Thunderbird/3.0.5

On 07/19/2010 03:30 PM, Jay K wrote:
>> Which version of autoconf generated the configure that produced the
>> output you are questioning?
> It is xz-4.999.9beta.tar.gz from http://tukaani.org/xz/.
> I was using gcc 4.2, but now 4.3 and I haven't retried with 4.3.5 yet.
> configure says:
> # Generated by GNU Autoconf 2.64 for XZ Utils 4.999.9beta.
> "For XZ Utils" sounds to me like maybe custom.

Nope, that sounds like stock (or maybe vendor-patched) 2.64, depending
on whether the xz maintainer builds his own autoconf or uses a distro.

Given these entries in later autoconf NEWS files:

* Major changes in Autoconf 2.66 (2010-07-02) [stable]
** The macros AC_TYPE_INT8_T, AC_TYPE_INT16_T, AC_TYPE_INT32_T, and
   AC_TYPE_INT64_T work again.  Regression introduced in 2.65.
* Major changes in Autoconf 2.65 (2009-11-21) [stable]
** The AC_TYPE_UINT64_T and AC_TYPE_INT64_T macros have been fixed to no
   longer mistakenly select a 32-bit type on some compilers (bug present
   since macros were introduced in 2.59c).

The bug thus appears to merely be that xz ran a too-old version of
autoconf, where AC_TYPE_UINT64_T was buggy for your compiler.  The bug
has hopefully already been fixed in newer autoconf, and running
'autoreconf' with 2.66 (or even better, with the pending 2.67)
installed, should create a configure file for xz that no longer has the
bug for your platform.

Eric Blake   address@hidden    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]