mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: Rich Felker <dalias@aerifal.cx>
Cc: musl@lists.openwall.com
Subject: loff_t definition in <fcntl.h> (vs. glibc in <sys/types.h>)
Date: Wed, 16 Oct 2019 23:28:38 +0200	[thread overview]
Message-ID: <20191016212835.GA17420@dell5510> (raw)

Hi Rich,

what is the reason for loff_t being defined in <fcntl.h> ?
It was defined some time ago, in v0.9.5.

glibc (and thus uclibc; + also Bionic) has it in <sys/types.h>, defined long
time before.  Who is correct? I guess loff_t not being posix, therefore it
shouldn't be in <sys/types.h> ?

I'm asking because it'd be nice to have it for both in single header
(portability).

Kind regards,
Petr


             reply	other threads:[~2019-10-16 21:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-16 21:28 Petr Vorel [this message]
2019-10-16 21:53 ` Rich Felker
2019-10-17 22:52   ` Petr Vorel
2019-10-18  1:21     ` Rich Felker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191016212835.GA17420@dell5510 \
    --to=petr.vorel@gmail.com \
    --cc=dalias@aerifal.cx \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).