fseek() vs. fseeko()

Ralf Corsepius ralf.corsepius@rtems.org
Wed Jun 20 11:08:00 GMT 2012

On 06/19/2012 07:11 PM, 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.

This could apply to Cygwin, I don't know, but I am pretty sure it's 
possible for RTEMS, which had never supported fseeko64 etc.

 From my point of view, the whole issue boils down to what Sebastian 
wrote in his initial posting:
  newlib assuming "sizeof(off_t) <= sizeof(long)"
and the code being cluttered with hard-coded casts.

That said, I hope to be able to come up with a patch later this week.


More information about the Newlib mailing list