From: Dave Hansen <haveblue@us.ibm.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: compile problem with gcc 2.95
Date: Mon, 29 Aug 2005 11:28:36 -0700 [thread overview]
Message-ID: <1125340116.26108.12.camel@localhost> (raw)
I know it's an ancient compiler, but last time I checked it is still
faster at runtime than the 3.x versions. If it's not going to be
supported, it would probably be nice to at least detect that in the
build system. I've confirmed that it works just fine with gcc 3.3.
dave@spirit:~/bin/git$ make
gcc -o rev-cache.o -c -g -O2 -Wall '-DSHA1_HEADER=<openssl/sha.h>'
rev-cache.c
In file included from rev-cache.c:2:
cache.h:107: field `name' has incomplete type
cache.h:290: field `base' has incomplete type
cache.h:303: field `pack_name' has incomplete type
cache.h:318: field `name' has incomplete type
make: *** [rev-cache.o] Error 1
dave@spirit:~/bin/git$ gcc -v
Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs
gcc version 2.95.4 20011002 (Debian prerelease)
> struct cache_entry {
...
> char name[]; <--- cache.h:107
> };
-- Dave
next reply other threads:[~2005-08-29 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-29 18:28 Dave Hansen [this message]
2005-08-29 19:10 ` compile problem with gcc 2.95 Junio C Hamano
2005-08-30 4:39 ` [HOWTO] Reverting an existing commit Junio C Hamano
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=1125340116.26108.12.camel@localhost \
--to=haveblue@us.ibm.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 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).