git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mike Ralphson" <mike.ralphson@gmail.com>
To: "Johannes Sixt" <j.sixt@viscovery.net>
Cc: "Junio C Hamano" <gitster@pobox.com>,
	git@vger.kernel.org, "Brandon Casey" <casey@nrlssc.navy.mil>
Subject: Re: [PATCH] Makefile: update the default build options for AIX
Date: Wed, 7 May 2008 15:20:45 +0100	[thread overview]
Message-ID: <e2b179460805070720o4028a841t6eabe9c1668a7a9f@mail.gmail.com> (raw)
In-Reply-To: <4821AB32.8090700@viscovery.net>

2008/5/7 Johannes Sixt <j.sixt@viscovery.net>:
> Mike Ralphson schrieb:
>
> > 2008/5/7 Johannes Sixt <j.sixt@viscovery.net>:
>  So you we in the same boat.
>
>  > The warnings are harmless, though untidy.
>  > I don't believe it's anything to do with _LARGE_FILES. Could you try
>  > building first with one commented out, then the other? I don't think I
>  > have access to a 4.3.3 box any more.
>
>  Untidy, yes; harmless: not necessarily. It has a lot to do with _LARGE_FILES.
>
>  The #define fopen in git-compat-util.h essentially defeats the effect of
>  _LARGE_FILES as far as fopen() calls are concerned: If
>  FREAD_READS_DIRECTORIES is not defined, fopen() would be redirected to
>  fopen64(), but when it is defined, it is redirected to git_fopen(), which
>  in turn uses fopen() instead of fopen64() (due to the #undef in
>  compat/fopen.c).
>
>  This might be dangerous if some other function of the f*64() family uses
>  the FILE* that the fopen() call returned. I don't know if there is such a
>  usage pattern somewhere in git.
>
>  Why did you need _LARGE_FILES in the first place?

Welcome aboard!

I was seeing test failures in t5302-pack-index.sh

Specifically tests 9 and 20
#   9: index v2: force some 64-bit offsets with pack-objects
#   20: create a stealth corruption in a delta base reference

These tests seem to be skipped these days if off_t isn't large enough,
I preferred the passing tests to the skipped ones. Maybe it isn't an
issue in the real world.

Mike

  reply	other threads:[~2008-05-07 14:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07  8:35 [PATCH] Makefile: update the default build options for AIX Mike Ralphson
2008-05-07 11:57 ` Johannes Sixt
2008-05-07 12:51   ` Mike Ralphson
2008-05-07 13:05     ` Mike Ralphson
2008-05-07 13:14     ` Johannes Sixt
2008-05-07 14:20       ` Mike Ralphson [this message]
2008-05-07 14:38       ` Brandon Casey
2008-05-07 15:15         ` Mike Ralphson
2008-05-07 15:39           ` Johannes Sixt
2008-05-07 15:40           ` Brandon Casey
2008-05-07 16:04             ` Junio C Hamano
2008-05-07 16:20               ` Mike Ralphson
2008-05-07 17:36                 ` Brandon Casey
2008-05-07 17:34               ` [PATCH] compat/fopen.c: avoid clobbering the system defined fopen macro Brandon Casey
2008-05-08  7:27                 ` Mike Ralphson
2008-05-08  7:34                   ` Johannes Sixt
2008-05-08  7:59                     ` Mike Ralphson
2008-05-08 10:37                   ` H.Merijn Brand
2008-05-16 10:19   ` [PATCH] Makefile: update the default build options for AIX Mike Ralphson
2008-05-16 13:37     ` Johannes Sixt

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=e2b179460805070720o4028a841t6eabe9c1668a7a9f@mail.gmail.com \
    --to=mike.ralphson@gmail.com \
    --cc=casey@nrlssc.navy.mil \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j.sixt@viscovery.net \
    /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).