From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: bill lam <cbill.lam@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [ANNOUNCE] GIT 1.6.1
Date: Thu, 25 Dec 2008 12:42:15 +0100 [thread overview]
Message-ID: <49537197.1000805@lsrfire.ath.cx> (raw)
In-Reply-To: <20081225102527.GB8451@b2j>
bill lam schrieb:
>> 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
>
> and this is the error logged.
>
> GIT_VERSION = 1.6.1
> * new build flags or prefix
> In file included from /usr/include/netinet/in.h:24,
> from git-compat-util.h:78,
> from builtin.h:4,
> from fast-import.c:142:
> /usr/include/stdint.h:136: error: conflicting types for ‘uint32_t’
> /usr/include/stdint.h:52: error: previous declaration of ‘uint32_t’ was here
> fast-import.c: In function ‘parse_progress’:
> fast-import.c:2339: warning: ignoring return value of ‘fwrite’, declared with attribute warn_unused_result
> make: *** [fast-import.o] Error 1
>
> version of gcc:
> gcc (Ubuntu 4.3.2-1ubuntu11) 4.3.2
I don't get any error on Ubuntu 8.10 on x86_64 (but several of those
warnings about ignored return values), neither with the tar file nor a
cloned repository (in the former case I had to add a "make configure"
step, though).
Line 52 of /usr/include/stdint.h:
typedef unsigned int uint32_t;
Lines 134-136 of /usr/include/stdint.h:
#if __WORDSIZE == 64
typedef long int intmax_t;
typedef unsigned long int uintmax_t;
If you get to line 136, you probably are on a 64 bit installation, too,
correct?
configure seems to be confused. What happens if you take it out of the
equation, i.e. run the following commands?
$ make distclean
$ make prefix=/usr
René
next prev parent reply other threads:[~2008-12-25 11:43 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 [this message]
2008-12-25 14:09 ` bill lam
2008-12-25 18:50 ` Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49537197.1000805@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=cbill.lam@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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 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 NNTP newsgroup(s).