pcp
[Top] [All Lists]

Build failure in dev - papi-related

To: pcp <pcp@xxxxxxxxxxx>
Subject: Build failure in dev - papi-related
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Sun, 1 Mar 2015 22:02:17 -0500 (EST)
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <586030531.17901563.1425265076705.JavaMail.zimbra@xxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: +fbPqZ9Ts+PkuWJTSKq9ng19X30Tww==
Thread-topic: Build failure in dev - papi-related
Everything was good on Friday when I left :) ... but no longer.
(this was with a working pcp-pmda-papi build too, and using the
papi-5.2.0-5.fc20.x86_64 version of PAPI from Fedora20).

$ ./Makepkgs 

== Cleaning build tree for packaging build
Wrote: /source/git/pcp/build/tar/pcp-3.10.3.src.tar.gz

== Preparing fresh build tree for packaging build

== Configuring pcp, log is in /source/git/pcp/Logs/pcp (--prefix=/usr 
--exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc 
--datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 
--libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib 
--mandir=/usr/share/man)

Configure failed, see log in /source/git/pcp/Logs/pcp
configure: error: Package requirements (check) were not met:

No package 'check' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables papi_CFLAGS
and papi_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.


--
Nathan

<Prev in Thread] Current Thread [Next in Thread>