public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fw at deneb dot enyo.de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/26255] <netdb.h> references <rpc/netdb.h>, but the latter is no longer installed
Date: Sat, 18 Jul 2020 09:11:03 +0000 [thread overview]
Message-ID: <bug-26255-131-7vcjX85HiO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26255-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26255
Florian Weimer <fw at deneb dot enyo.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |2.32
CC| |fw at deneb dot enyo.de
--- Comment #2 from Florian Weimer <fw at deneb dot enyo.de> ---
Fixed for glibc 2.32 with:
commit 76b8442db51a8976de19934638a42532a3af607f
Author: Florian Weimer <fweimer@redhat.com>
Date: Fri Jul 17 15:19:35 2020 +0200
Move <rpc/netdb.h> from sunrpc to inet
Restore <rpc/netdb.h> as an installed header. Delete the dummy header
resolv/rpc/netdb.h because inet is not an optional glibc component
(so its <rpc/netdb.h> is always available).
Fixes commit acb527929d0c2b3bb0798472c42ddb3203729708 ("Move
non-deprecated RPC-related functions from sunrpc to inet") in
combination with commit 5500cdba4018ddbda7909bc7f4f9718610b43cf0
("Remove --enable-obsolete-rpc configure flag").
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-07-18 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 2:53 [Bug libc/26255] New: " bero at lindev dot ch
2020-07-17 7:49 ` [Bug libc/26255] " fweimer at redhat dot com
2020-07-18 9:11 ` fw at deneb dot enyo.de [this message]
2020-12-04 8:53 ` fweimer at redhat dot com
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-26255-131-7vcjX85HiO@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).