This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.

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

Re: using _FILE_OFFSET_BITS=64 with a non-gcc compiler

To: drepper at redhat dot com (Ulrich Drepper)
Subject: Re: using _FILE_OFFSET_BITS=64 with a non-gcc compiler
From: Bruno Haible <haible at ilog dot fr>
Date: Tue, 13 Nov 2001 20:31:07 +0100 (CET)
Cc: libc-alpha at sources dot redhat dot com
References: <15343.63100.268838.501398@honolulu.ilog.fr><m3u1vzc20h.fsf@myware.mynet><15345.1321.291057.835146@honolulu.ilog.fr><m31yj2a8qe.fsf@myware.mynet>

[Get raw message]

Ulrich Drepper writes:
> Of course it does.  Every symbol defined in system headers which is in
> the user namespace (and all these symbols are) must be defined or
> reserved in the standard.  Otherwise it's a violation.

Are 'readdir64' and 'getrlimit64' defined or reserved in the standard?

Are 'dirent64' and 'rlimit64' defined or reserved in the standard?

Bruno

Follow-Ups:
- Re: using _FILE_OFFSET_BITS=64 with a non-gcc compiler
  - From: Ulrich Drepper
- Re: using _FILE_OFFSET_BITS=64 with a non-gcc compiler
  - From: Martin v. Loewis

References:
- using _FILE_OFFSET_BITS=64 with a non-gcc compiler
  - From: Bruno Haible
- Re: using _FILE_OFFSET_BITS=64 with a non-gcc compiler
  - From: Ulrich Drepper
- Re: using _FILE_OFFSET_BITS=64 with a non-gcc compiler
  - From: Bruno Haible
- Re: using _FILE_OFFSET_BITS=64 with a non-gcc compiler
  - From: Ulrich Drepper

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