From: Isaac Dunham <idunham@lavabit.com>
To: musl@lists.openwall.com
Subject: Re: [PATCH]_BSD_SOURCE for musl, take 2.
Date: Tue, 22 May 2012 16:19:31 -0700 [thread overview]
Message-ID: <20120522161931.63139ff9@newbook> (raw)
In-Reply-To: <20120522152256.GS163@brightrain.aerifal.cx>
On Tue, 22 May 2012 11:22:56 -0400
Rich Felker <dalias@aerifal.cx> wrote:
> On Mon, May 21, 2012 at 11:31:58AM -0700, Isaac Dunham wrote:
> > Here's a second verion of the patch, with all the issues below
> > addressed.
>
> Looks good. A few more things, mostly just questions to make sure
> stuff is ok..
>
> > I'm still declaring bsd_signal if _BSD_SOURCE is defined, because it
> > uses the signature of BSD signal().
>
> Is there a reason for this? bsd_signal was a legacy SUSv3 function
> removed in SUSv4/POSIX-2008, which was originally added mainly so that
> programs written for BSD signal semantics could do:
>
> #define signal bsd_signal
>
> on non-BSD systems and still work. On glibc and musl it's utterly
> useless since signal, by default, has BSD semantics. (POSIX allows
> either and only BSD is sane.)
> I doubt any code for BSD would ever be calling bsd_signal, as the
> whole purpose of it is to provide an alternate function with BSD
> behavior on non-BSD systems.
I had not realized that musl used BSD semantics. You can drop that, if
you want.
> > diff --git a/include/netinet/tcp.h b/include/netinet/tcp.h
> > index c8a1a4b..797ce68 100644
> > --- a/include/netinet/tcp.h
> > +++ b/include/netinet/tcp.h
> > @@ -2,5 +2,22 @@
> > #define _NETINET_TCP_H
> >
> > #define TCP_NODELAY 1
> > +#if defined(_GNU_SOURCE) || defined(_BSD_SOURCE)
> > +#include <sys/types.h>
> > +#include <sys/socket.h>
> > +#define TCP_MAXSEG 2
> > +#define TCP_CORK 3
> > +#define TCP_KEEPIDLE 4
> > [...]
>
> TCP_* is in the reserved namespace for this header, so I think it
> would be reasonable to define all the macros unconditionally. What
> about the two includes, though? If they're needed to make GNU/BSD
> programs work, we should still keep the check just for them.
I'm not sure whether the includes are expected by some programs.
> > diff --git a/include/unistd.h b/include/unistd.h
> > index b1a84d7..0112276 100644
> > --- a/include/unistd.h
> > +++ b/include/unistd.h
> > @@ -16,6 +16,12 @@ extern "C" {
> > #define SEEK_CUR 1
> > #define SEEK_END 2
> >
> > +#if defined(_BSD_SOURCE) && !defined(L_SET)
> > +#define L_SET SEEK_SET
> > +#define L_INCR SEEK_CUR
> > +#define L_XTND SEEK_END
>
> Is L_SET defined somewhere else?
Not in the patch; glibc has it in sys/file.h, which I somehow missed.
I'm inclined to say keep the test and I'll send a patch for that, but
take your pick.
For unknown reasons it looks like sys/file.h has no content except that
protected by _GNU_SOURCE | _BSD_SOURCE -- which sounds like an
unnecessary test.
Isaac Dunham
prev parent reply other threads:[~2012-05-22 23:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 6:26 _BSD_SOURCE support for musl ready Isaac Dunham
2012-05-21 12:42 ` Isaac Dunham
2012-05-21 13:36 ` Rich Felker
2012-05-21 17:19 ` Isaac Dunham
2012-05-21 17:43 ` Rich Felker
2012-05-21 18:31 ` [PATCH]_BSD_SOURCE for musl, take 2 Isaac Dunham
2012-05-22 15:22 ` Rich Felker
2012-05-22 23:19 ` 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=20120522161931.63139ff9@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).