fseek() vs. fseeko()

[Sebastian Huber]

On 19/06/12 19:11, Corinna Vinschen wrote:
> On Jun 19 18:27, Ralf Corsepius wrote:
>>> Ok, then this is a bug in the RTEMS targets using 64-bit off_t.
>> No. This is a bug in newlib.
>>
>> fseeko etc. are supposed to take abstract types "off_t".
>>
>> RTEMS relies upon this assumption, but obviously can't handle this.
>>
>>> Since>  the fseeko64() etc. are non-standard this should be
>> invisible for the>  user.
>>
>> Agreed. They should not be used anywhere and be removed from newlib.
> That's obviously not possible for backward compatibility.
>
>

I don't know if we can assume sizeof(off_t) >= sizeof(long).  Suppose we 
can, then we may implement the fseek(), _fseek_r(), and fseeko() with a 
_fseeko_r(). The internal state seems to use the proper integer types.

-- 
Sebastian Huber, embedded brains GmbH

Address : Obere Lagerstr. 30, D-82178 Puchheim, Germany
Phone   : +49 89 18 90 80 79-6
Fax     : +49 89 18 90 80 79-9
E-Mail  : sebastian.huber@embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.