From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: sys/queue.h
Date: Fri, 28 Jun 2013 18:19:30 -0400 [thread overview]
Message-ID: <20130628221930.GF29800@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAK4o1Wwg_Yg-K9GcQJya5ZsuaOb4scNo17dbKURxChwixLbUrw@mail.gmail.com>
On Fri, Jun 28, 2013 at 10:54:03PM +0100, Justin Cormack wrote:
> On Fri, Jun 28, 2013 at 10:47 PM, John Spencer
> <maillist-musl@barfooze.de> wrote:
> > On 06/28/2013 11:29 PM, Justin Cormack wrote:
> >>
> >> I just found some code that uses sys/queue.h
> >>
> >> This is actually just macros and typedefs as far as I can see, no
> >> actual code at all. glibc simply uses the header file from BSD as far
> >> as I can see, so this would be fairly trivial to add.
> >
> >
> >
> > but it has an ugly 3-clause BSD license.
>
> That could be fixed by rewriting it I guess. Not sure it is
> copyrightable even...
Unlike most headers which are not copyrightable, this one is 100%
code. I agree the code is fairly generic and standard, though.
> > relying on its existence is highly fragile so most programs that use it have
> > their own copy somewhere in-tree.
> > and if not, it's a bug.
>
> Will complain to upstream.
For now, I think that's the best approach. It it becomes a widespread
issue that's hard to get fixed upstream, we can consider adding it.
However unlike some nonstandard interfaces where you reduce bloat by
having a shared copy in libc, this header is entirely inlined macros,
and it makes no difference from a bloat standpoint whether it's
inlined from /usr/include/sys/queue.h or ./include/queue.h.
Rich
prev parent reply other threads:[~2013-06-28 22:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 21:29 sys/queue.h Justin Cormack
2013-06-28 21:47 ` sys/queue.h John Spencer
2013-06-28 21:54 ` sys/queue.h Justin Cormack
2013-06-28 22:19 ` Rich Felker [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=20130628221930.GF29800@brightrain.aerifal.cx \
--to=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).