public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "arjan at linux dot intel.com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nis/14305] New: 2.16(candidate) --enable-obsolete-rpc is not sufficient for libtirpc
Date: Wed, 27 Jun 2012 17:14:00 -0000 [thread overview]
Message-ID: <bug-14305-131@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=14305
Bug #: 14305
Summary: 2.16(candidate) --enable-obsolete-rpc is not
sufficient for libtirpc
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: nis
AssignedTo: unassigned@sourceware.org
ReportedBy: arjan@linux.intel.com
CC: kukuk@suse.de
Classification: Unclassified
trying to use libtirpc with the 2.16 glibc (candidate), glibc compiled with
--enable-obsolete-rpc:
/usr/lib/gcc/x86_64-unknown-linux-gnu/4.7.1/../../../../lib64/libtirpc.so:
undefined reference to `svc_auth_none'
/usr/lib/gcc/x86_64-unknown-linux-gnu/4.7.1/../../../../lib64/libtirpc.so:
undefined reference to `_svcauth_none'
/usr/lib/gcc/x86_64-unknown-linux-gnu/4.7.1/../../../../lib64/libtirpc.so:
undefined reference to `_des_crypt_call'
these symbols seem hidden, and previously, the old rpc stuff unhid them.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2012-06-27 17:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 17:14 arjan at linux dot intel.com [this message]
2012-06-27 18:23 ` [Bug nis/14305] " aj at suse dot de
2012-06-27 18:29 ` aj at suse dot de
2012-06-27 18:30 ` arjan at linux dot intel.com
2012-06-27 18:32 ` aj at suse dot de
2012-06-27 18:35 ` aj at suse dot de
2012-07-24 4:17 ` carlos_odonell at mentor dot com
2012-08-11 18:17 ` vapier at gentoo dot org
2012-08-12 5:05 ` aj at suse dot de
2014-06-18 4:31 ` 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-14305-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.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).