public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/30247] all socket options should be available with _XOPEN_SOURCE. not merely _GNU_SOURCE
Date: Tue, 04 Apr 2023 09:58:36 +0000 [thread overview]
Message-ID: <bug-30247-131-OI3o6Wxpbe@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30247-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30247
Andreas Schwab <schwab@linux-m68k.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |24532
--- Comment #1 from Andreas Schwab <schwab@linux-m68k.org> ---
This has changed in commit 7854ebf8ed to fix bug 24532. __USE_MISC is probably
too strict.
Referenced Bugs:
https://sourceware.org/bugzilla/show_bug.cgi?id=24532
[Bug 24532] conform/arpa/inet.h failures due to linux kernel 64-bit time_t
changes
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-04-04 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 0:24 [Bug network/30247] New: " jscott at posteo dot net
2023-03-21 4:18 ` [Bug network/30247] " sam at gentoo dot org
2023-04-04 9:58 ` schwab@linux-m68k.org [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=bug-30247-131-OI3o6Wxpbe@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).