Date: Sun, 10 Dec 2000 09:41:22 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Peter J. Farley III" <pjfarley AT banet DOT net>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Why are we using offset_t and not off64_t?
In-Reply-To: <5.0.2.1.0.20001209125228.025cbec0@pop5.banet.net>
Message-ID: <Pine.SUN.3.91.1001210093927.700K-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sat, 9 Dec 2000, Peter J. Farley III wrote:

> I'm finally getting around to putting in the FAT32 support to the new 
> fcntl, and in looking up all the types and definitions needed, I see 
> that for "long long int" offsets we are using "offset_t" instead of 
> "off64_t", such as is used in glibc-2.1.3.  Can anyone enlighten me why 
> we are doing this?

Whatever the reasons are, we could typedef off64_t to be the same as 
offset_t.

> Why not just lift the __USE_LARGEFILE64 and 
> __USE_FILE_OFFSET64 code from glibc's posix/sys/types.h, suitably 
> modified for DJGPP?

What do you need these __USE_* symbols for?

I'd advise against using symbols we don't need, because some configure 
script might test for them and draw wrong conclusions.