mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Isaac Dunham <idunham@lavabit.com>
To: musl@lists.openwall.com
Subject: Re: getpass misplaced
Date: Sun, 20 May 2012 20:38:00 -0700	[thread overview]
Message-ID: <20120520203800.3ee079d0@newbook> (raw)
In-Reply-To: <20120521030106.GD163@brightrain.aerifal.cx>

On Sun, 20 May 2012 23:01:06 -0400
Rich Felker <dalias@aerifal.cx> wrote:
> > This has me down to 22 headers that still need work/reviewing.
> > Here's the TODO for _BSD_SOURCE:
Note: the TODO is a list of files to review autogenerated by grepping
for MISC or BSD in headers from glibc.  Some of these can be expected
to work with _BSD_SOURCE already, because glibc uses so many feature
tests.
> > 
> > include/tgmath.h
> 
> This is purely C99 stuff; I don't think GNU would add anything.
> 
> > include/glob.h
> 
> We don't support the extensions here, and even if we want to have the
> macros for extension flags, they seem to be in the reserved namespace
> and thus ok to defined unconditionall.
> 
> > include/shadow.h
> > include/endian.h
> 
> These are nonstandard and in principle don't need any feature test
> macros. However, we use them in endian.h so that other headers can
> include endian.h.
> 
> > <netinet/in.h> could cause breakage without extension.  I forget
> > exactly what the problem was, though.
> ..what?
Extremely bad wording on my part.
_BSD_SOURCE or _GNU_SOURCE make these structs available in glibc:
group_req, group_source_req, group_filter, ip_msfilter

I had forgotten which structs as of the last mail.
I'd expect breakage without them, though I guess we could wait and see.

Isaac Dunham



  reply	other threads:[~2012-05-21  3:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-21  2:25 Isaac Dunham
2012-05-21  3:01 ` Rich Felker
2012-05-21  3:38   ` Isaac Dunham [this message]
2012-05-21  4:52   ` Question on setjmp.h Isaac Dunham
2012-05-21  4:53     ` Rich Felker

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=20120520203800.3ee079d0@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).