From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: libtirpc and redeclared bindresvport/bindresvport_sa
Date: Mon, 16 Jun 2014 18:55:00 -0000 [thread overview]
Message-ID: <539F3D84.5060005@cygwin.com> (raw)
In-Reply-To: <5384368E.4000707@lysator.liu.se>
On 2014-05-27 01:54, Peter Rosin wrote:
> I ran into this problem [1] when doing some RPC coding, and went
> searching for a resolution. But I came up empty. Was there any
> further discussion?
AFAICS that thread is the extent of it.
> Is this what is holding up the libvirt ITP?
No, I think that would just be Eric's schedule.
> Meanwhile, libtirpc-0.2.4 has been released, but this particular
> problem probably remains [2].
The issue is an upstream one, and as you note, exists even on glibc
platforms. The function originates in sunrpc code, which is now
maintained as libtirpc, but because it was treated as a generic
networking function in glibc (declared in <netinet/in.h>), it is still
provided even if the now-obsolete RPC code is not (IOW if glibc is
configured w/o --enable-obsolete-rpc).
Since these are just redundant declarations and not conflicting ones,
each existing for good reason, and the identical situation exists on
glibc platforms, I don't think this is really an issue that needs to be
addressed at this time. If a real-world failure does occur, we can
reassess the situation then.
Yaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2014-06-16 18:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 11:50 Peter Rosin
2014-06-16 18:55 ` Yaakov Selkowitz [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=539F3D84.5060005@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin@cygwin.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.
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).