From: Leo Famulari <leo@famulari.name>
To: 29970@debbugs.gnu.org
Subject: [bug#29970] [PATCH 3/4] gnu: rpcbind: Build with libnsl.
Date: Wed, 3 Jan 2018 19:30:55 -0500 [thread overview]
Message-ID: <bfc82c6c763ae714d87a18314f21bd8bea3e77fa.1515025855.git.leo@famulari.name> (raw)
In-Reply-To: <a72d768bb8f8ce0668099c964999a505c2541032.1515025855.git.leo@famulari.name>
In-Reply-To: <a72d768bb8f8ce0668099c964999a505c2541032.1515025855.git.leo@famulari.name>
* gnu/packages/onc-rpc.scm (rpcbind)[inputs]: Add libnsl.
---
gnu/packages/onc-rpc.scm | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/gnu/packages/onc-rpc.scm b/gnu/packages/onc-rpc.scm
index 38f2f5a1d..07841e7e2 100644
--- a/gnu/packages/onc-rpc.scm
+++ b/gnu/packages/onc-rpc.scm
@@ -87,7 +87,8 @@ IPv4 and IPv6. ONC RPC is notably used by the network file system (NFS).")
`(#:configure-flags
`("--with-systemdsystemunitdir=no" "--enable-warmstarts")))
(inputs
- `(("libtirpc" ,libtirpc)))
+ `(("libnsl" ,libnsl)
+ ("libtirpc" ,libtirpc)))
(native-inputs
`(("pkg-config" ,pkg-config)))
(home-page "http://rpcbind.sourceforge.net/")
--
2.15.1
next prev parent reply other threads:[~2018-01-04 0:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 0:28 [bug#29970] core-updates: libtirpc, rpcbind, nfs-utils Leo Famulari
2018-01-04 0:30 ` [bug#29970] [PATCH 1/4] gnu: libtirpc: Update to 1.0.2 Leo Famulari
2018-01-04 0:30 ` [bug#29970] [PATCH 2/4] gnu: Add libnsl Leo Famulari
2018-01-06 21:41 ` Marius Bakke
2018-01-04 0:30 ` Leo Famulari [this message]
2018-01-06 21:44 ` [bug#29970] [PATCH 3/4] gnu: rpcbind: Build with libnsl Marius Bakke
2018-01-04 0:30 ` [bug#29970] [PATCH 4/4] gnu: nfs-utils: Adapt to changes in glibc 2.26 Leo Famulari
2018-01-06 21:45 ` Marius Bakke
2018-01-06 21:34 ` [bug#29970] [PATCH 1/4] gnu: libtirpc: Update to 1.0.2 Marius Bakke
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bfc82c6c763ae714d87a18314f21bd8bea3e77fa.1515025855.git.leo@famulari.name \
--to=leo@famulari.name \
--cc=29970@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).