From: Junio C Hamano <gitster@pobox.com>
To: bill lam <cbill.lam@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.6.1
Date: Thu, 25 Dec 2008 10:50:37 -0800 [thread overview]
Message-ID: <7vvdt884xu.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20081225102527.GB8451@b2j> (bill lam's message of "Thu, 25 Dec 2008 18:25:27 +0800")
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
next prev parent reply other threads:[~2008-12-25 18:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-25 6:36 [ANNOUNCE] GIT 1.6.1 Junio C Hamano
2008-12-25 8:32 ` Christian MICHON
2008-12-25 10:00 ` bill lam
2008-12-25 10:13 ` Junio C Hamano
2008-12-25 10:25 ` bill lam
2008-12-25 11:42 ` René Scharfe
2008-12-25 14:09 ` bill lam
2008-12-25 18:50 ` Junio C Hamano [this message]
2008-12-26 14:42 ` bill lam
2008-12-25 18:53 ` Pau Garcia i Quiles
2008-12-26 14:33 ` bill lam
2008-12-25 11:44 ` Heikki Orsila
2008-12-26 1:38 ` Sitaram Chamarty
2008-12-27 1:56 ` Nicolas Pitre
2008-12-27 10:31 ` [ANNOUNCE] MSYSGIT 1.6.1 Steffen Prohaska
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vvdt884xu.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=cbill.lam@gmail.com \
--cc=git@vger.kernel.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://80x24.org/mirrors/git.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).