From: Junio C Hamano <gitster@pobox.com>
Date: Thu, 25 Dec 2008 18:50:37 GMT
Subject: Re: [ANNOUNCE] GIT 1.6.1
Message-ID: <7vvdt884xu.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <20081225102527.GB8451@b2j>

bill lam <cbill.lam@gmail.com> writes:

>> Why are you building with NO_UINTMAX_T to begin with?  Isn't ubuntu 8.10 a
>> recent enough platform that ships with modern enough header files that
>> define ANSI uintmax_t type?
>
> No, I did not do anything on that, 
>
> make clean
> ./configure --prefix=/usr
> make 

I do not use configure myself (use of configure is entirely optional, and
it is not tested often and core developers do not touch that part very
much --- in a sense, use of autoconf is a second-class citizen in our
build process); it is plausible that it has broken checks for detecting
the need of NO_UINTMAX_T.

Relevant part of configure.ac reads like this:

    # Define NO_UINTMAX_T if your platform does not have uintmax_t
    AC_CHECK_TYPE(uintmax_t,
    [NO_UINTMAX_T=],
    [NO_UINTMAX_T=YesPlease],[
    #include <inttypes.h>
    ])
    AC_SUBST(NO_UINTMAX_T)

and I do not see anything suspicious there...

Running "./configure --verbose" might leave some clues in config.log; for
me on my primary development box (Debian on x86_64), the relevant part
passes the test (iow, inclusion of inttypes.h does give a working
uintmax_t type) like this:

    configure:5709: checking for uintmax_t
    configure:5742: cc -c -g -O2  conftest.c >&5
    configure:5748: $? = 0
    configure:5763: result: yes