From: Jonathan Nieder <jrnieder@gmail.com>
To: "Gabor Z. Papp" <gzp@papp.hu>
Cc: git@vger.kernel.org
Subject: Re: git 1.6.6.1 on glibc 2.2
Date: Sun, 24 Jan 2010 06:27:51 -0600 [thread overview]
Message-ID: <20100124122751.GA3265@progeny.tock> (raw)
In-Reply-To: <x6y6jn4txy@gzp>
Hi!
Gabor Z. Papp wrote:
> Hello all,
>
> trying to compile git 1.6.6.1 on Linux 2.4.37.7, glibc 2.2.5:
>
> read-cache.c: In function 'fill_stat_cache_info':
> read-cache.c:72: error: 'struct stat' has no member named 'st_ctim'
Thanks for the report. Perhaps:
$ grep -C3 st_ctim Makefile
# randomly break unless your underlying filesystem supports those sub-second
# times (my ext3 doesn't).
#
# Define USE_ST_TIMESPEC if your "struct stat" uses "st_ctimespec" instead of
# "st_ctim"
#
# Define NO_NSEC if your "struct stat" does not have "st_ctim.tv_nsec"
# available. This automatically turns USE_NSEC off.
#
# Define USE_STDEV below if you want git to care about the underlying device
Hope that helps,
Jonathan
next prev parent reply other threads:[~2010-01-24 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 11:35 git 1.6.6.1 on glibc 2.2 Gabor Z. Papp
2010-01-24 12:27 ` Jonathan Nieder [this message]
2010-01-24 15:09 ` Gabor Z. Papp
2010-01-24 17:40 ` Jonathan Nieder
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=20100124122751.GA3265@progeny.tock \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gzp@papp.hu \
/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.