All of lore.kernel.org
 help / color / mirror / Atom feed
From: bill lam <cbill.lam@gmail.com>
To: git@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.6.1
Date: Fri, 26 Dec 2008 22:42:50 +0800	[thread overview]
Message-ID: <20081226144250.GC7103@b2j> (raw)
In-Reply-To: <7vvdt884xu.fsf@gitster.siamese.dyndns.org>

On Thu, 25 Dec 2008, Junio C Hamano wrote:
> 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...

Thanks, I guess the configure is not part of the repository and I use
a legacy configure from earlier version. After I run the make
configure again, it is now ok.

-- 
regards,
====================================================
GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
唐詩093 駱賓王  在獄詠蟬
    西路蟬聲唱  南冠客思侵  那堪玄鬢影  來對白頭吟
    露重飛難進  風多響易沉  無人信高潔  誰為表予心

  reply	other threads:[~2008-12-26 14:44 UTC|newest]

Thread overview: 16+ 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
2008-12-26 14:42         ` bill lam [this message]
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-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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081226144250.GC7103@b2j \
    --to=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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.