This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Why fseeko always calls _llseek.?

From: James E Wilson <wilson at specifixinc dot com>
To: Chakravarthy Nelluri <chakri_in5 at yahoo dot com>
Cc: gcc-bugs at gcc dot gnu dot org
Date: Wed, 01 Sep 2004 17:14:20 -0700
Subject: Re: Why fseeko always calls _llseek.?
References: <20040901062636.8434.qmail@web12707.mail.yahoo.com>

Chakravarthy Nelluri wrote:

  Why fseeko always ends up calling _llseek on linux(
not sure how it behaves in other OS'es)?

Probably because it is supposed to.

Since this isn't a gcc bug report, or even a gcc question, I can't help you much further. Try looking at the ISO C standards, the POSIX standards, and/or the Single Unix Spec (SUSv2). Probably one of them covers this. Or you could try asking on one of the glibc mailing lists. -- Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

References:
- Why fseeko always calls _llseek.?
  - From: Chakravarthy Nelluri

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]