From: Isaac Dunham <idunham@lavabit.com>
To: musl@lists.openwall.com
Subject: Re: sys/signal.h, sys/dirent.h + bugzilla.
Date: Thu, 30 Aug 2012 14:56:46 -0700 [thread overview]
Message-ID: <20120830145646.00bd3990@newbook> (raw)
In-Reply-To: <20120824174335.GC27715@brightrain.aerifal.cx>
On Fri, 24 Aug 2012 13:43:35 -0400
Rich Felker <dalias@aerifal.cx> wrote:
> > I've seen sys/syscall.h previously. Easily fixed.
> > I have considered doing a glibc-header-compat package, which
> > provides various nonstandard headers (sys/ aliases, sys/queue.h,
> > etc.) out of tree. I don't think they belong in tree.
>
> I'm not sure how having a separate package for 5-10 one-line .h files
> is beneficial. Sounds like something the X.org folks would have come
> up with... especially if you want to package them with a 600k
> configure script. :-)
sys/queue.h is decidedly larger than that (more like 600 lines), and
there are a few other large headers containing mainly/only macros.
These are things I've seen a need for in several packages.
I'm thinking that _if_ I ship several macro headers purely for
compatibility, I might as well also have some aliases that make
building software easier.
Re configure scripts: in case you forgot, I've said a few time that I'd
rather edit config.mak. This could be handled quite easily in a few
lines of shell, with test.
> <sys/syscall.h> is the correct name; <syscall.h> is wrong. Neither is
> standard of course, but the former is the historical location and the
> latter seems to have been added by glibc at some point for no apparent
> reason.
Compatability with DEC libc (DEC only had <syscall.h>). In other words,
<sys/syscall.h> is historical for Linux, but <syscall.h> has history on
other platforms.
Isaac Dunham
prev parent reply other threads:[~2012-08-30 21:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 10:40 Daniel Cegiełka
2012-08-24 12:19 ` John Spencer
2012-08-24 12:32 ` Rich Felker
2012-08-24 13:10 ` idunham
2012-08-24 13:33 ` Gregor Richards
2012-08-24 17:43 ` Rich Felker
2012-08-30 21:56 ` Isaac Dunham [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=20120830145646.00bd3990@newbook \
--to=idunham@lavabit.com \
--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).