From: Michael Forney <mforney@mforney.org>
To: musl@lists.openwall.com
Subject: Re: Removing sys/sysmacros.h from sys/types.h
Date: Sat, 29 Jun 2019 15:11:23 -0700 [thread overview]
Message-ID: <CAGw6cBvptg8sXgjp_ZpPLcxtUkOP8qXMcQrLwR5NqmfJmhr76Q@mail.gmail.com> (raw)
In-Reply-To: <20190629214156.GM1506@brightrain.aerifal.cx>
On 2019-06-29, Rich Felker <dalias@libc.org> wrote:
>> I'm just curious if there is a good way to use these macros in
>> software that is otherwise portable without adding a configure script.
>> Most BSDs don't have sys/sysmacros.h, and now glibc and musl require
>> including sys/sysmacros.h to use them.
>>
>> It's a shame that while these macros are available on most unix-like
>> operating systems, they can't be accessed in a generic way.
>
> There's really not much of a use for them at all in portable software.
> Devices having "major/minor numbers", rather than dev_t just being an
> abstract identifier, is an anachronism that's not really compatible
> with exploding numbers of device types or operating systems that don't
> expose any idea of a type/major.
>
> If you really do need them, you should probably just search for them
> with a configure check, first for sys/sysmacros.h, then for any other
> historical places they might have been found in.
The case I'm interested in is implementing ls(1), which needs a way to
display the dev_t in a human readable way, and tar(1) since the ustar
format stores devmajor and devminor separately.
But anyway, I guess adding a configure script is the only reliable way
to use them. I wonder if any of the BSDs would consider adding
sys/sysmacros.h...
Thanks for your input.
prev parent reply other threads:[~2019-06-29 22:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 20:20 Benjamin Wright
2019-06-14 21:15 ` Rich Felker
2019-06-29 21:00 ` Michael Forney
2019-06-29 21:41 ` Rich Felker
2019-06-29 22:11 ` Michael Forney [this message]
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=CAGw6cBvptg8sXgjp_ZpPLcxtUkOP8qXMcQrLwR5NqmfJmhr76Q@mail.gmail.com \
--to=mforney@mforney.org \
--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).