From: Gregor Richards <gr@purdue.edu>
To: musl@lists.openwall.com
Subject: Re: sys/signal.h, sys/dirent.h + bugzilla.
Date: Fri, 24 Aug 2012 09:33:00 -0400 [thread overview]
Message-ID: <5037828C.3060809@purdue.edu> (raw)
In-Reply-To: <25665.132.241.65.118.1345813847.squirrel@lavabit.com>
On 08/24/12 09:10, idunham@lavabit.com wrote:
>> On Fri, Aug 24, 2012 at 02:19:55PM +0200, John Spencer wrote:
>>> On 08/24/2012 12:40 PM, Daniel CegieÅ*ka wrote:
>>>> Hi,
>>>>
>>>> e2fsprogs (misc/fsck.c) needs include/sys/signal.h, but musl installs
>>>> signal.h only in include/. symlink in Makefile?
>>>>
>>>> btw. the same situation: sys/dirent.h
>>> those are not posix, the package you're trying to compile is at fault
>>> here.
> it's util-*linux*, not util-posix - what do you expect? :P
>> Yes. We've already handled _some_ broken things like this by just
>> adding the nonsense alias for the header (as a wrapper rather than a
>> symlink, though; using symlinks is a bad idea because installing them
>> does not work well) but so far this is the only report I've seen of an
>> app needing these two
> 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.
>
> BTW, util-linux will probably need to check unistd.h for an adequate
> standards-support (_XOPEN_VERSION/_POSIX_VERSION). Allegedly, they
> support every libc out there, and a number of older ones don't even have
> <syscall.h>.
>
>
>
Ideally, these headers should contain
#ifndef _GNU_SOURCE
#error This is a nonstandard header.
#endif
Perhaps with _BSD_SOURCE too if the BSDs have similar wonko headers.
With valediction,
- Gregor Richards
next prev parent reply other threads:[~2012-08-24 13:33 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 [this message]
2012-08-24 17:43 ` Rich Felker
2012-08-30 21:56 ` Isaac Dunham
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=5037828C.3060809@purdue.edu \
--to=gr@purdue.edu \
--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).