From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Upstream nfs-utils not building on EL6 again
Date: Mon, 05 Jan 2015 08:28:54 -0500 [thread overview]
Message-ID: <54AA9196.1030908@RedHat.com> (raw)
In-Reply-To: <E046B731-3611-4E1D-8C88-42134819B123@oracle.com>
Hey Chuck,
On 01/02/2015 04:16 PM, Chuck Lever wrote:
> checking pkg-config is at least version 0.9.0... yes
> checking for TIRPC... no
> configure: error: libtirpc not found.
> make: *** No rule to make target `all'. Stop.
> [cel@manet nfs-utils]$ sudo yum install libtirpc-devel
> Loaded plugins: security
> Setting up Install Process
> Package libtirpc-devel-0.2.1-10.el6.x86_64 already installed and latest version
> Nothing to do
> [cel@manet nfs-utils]$
>
> After the following patch is reverted, the build is successful:
>
> commit 853406302d7a506605ce64592e77fd722b5e23d5
> Author: Yann E. MORIN <yann.morin.1998@free.fr>
> Date: Sat Dec 13 10:16:38 2014 -0500
>
> configure: use pkg-config to find libtirpc
>
> Perhaps the new "[libtirpc >= 0.2.4]” check is too aggressive.
No... The problem is litbtirpc does not register with the pkg-config
program. So "pkg-config --exists libtirpc" fails even when libtirpc
is installed.
I would like to maintain being able to compile upstream code on
legacy OSs so I'm looking into how painful it will be to
revert this patch...
steved.
prev parent reply other threads:[~2015-01-05 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 21:16 Upstream nfs-utils not building on EL6 again Chuck Lever
2015-01-05 13:28 ` Steve Dickson [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=54AA9196.1030908@RedHat.com \
--to=steved@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.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