Package Details: papi 7.2.0-1

Git Clone URL: https://aur.archlinux.org/papi.git (read-only, click to copy)
Package Base: papi
Description: Performance Application Programming Interface
Upstream URL: http://icl.cs.utk.edu/papi
Keywords: counter libpapi performance
Licenses: BSD
Conflicts: libpfm
Provides: libpfm
Submitter: jedbrown
Maintainer: forcegk
Last Packager: forcegk
Votes: 22
Popularity: 0.023562
First Submitted: 2009-11-09 21:53 (UTC)
Last Updated: 2025-06-27 08:03 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

wuxb commented on 2022-05-16 21:37 (UTC)

@gamezelda Fixed. Thanks for the msg!

gamezelda commented on 2022-05-16 19:55 (UTC)

Fails to build after the recent GCC 12 update in the Arch repos. The problem is inside the vendored libpfm4 dependency, see also: https://sourceforge.net/p/perfmon2/mailman/perfmon2-devel/thread/cd043334-18bf-213b-4e35-39c63e250720@redhat.com/

The post above includes a patch. Another simpler workaround is to set -Wno-error=use-after-free, i.e. as follows in the PKGBUILD:

-  export CFLAGS="-fPIC ${CFLAGS}"
+  export CFLAGS="-fPIC -Wno-error=use-after-free ${CFLAGS}"

eolianoe commented on 2019-02-16 11:02 (UTC)

@wuxb: I can't reproduce your error, try to upgrade and reboot your machine and use pure makepkg (not yay).

eolianoe commented on 2019-02-15 11:21 (UTC)

@wuxb: no trouble on my side even on a clean chroot. Could you share the error message?

cniethammer commented on 2018-10-12 18:09 (UTC)

I can confirm, that PAPI 5.6.0 does not build with GCC 8.2.1. The issue is fixed by the PAPI/libpfm4 developers but they did not come out with an official stable PAPI release including these fixes yet.

poinu commented on 2018-10-10 07:51 (UTC)

This version of PAPI fails to compile with GCC 8.2.1 for me. It builds fine with GCC 6.4.1. Can anybody check?

eolianoe commented on 2017-09-24 10:58 (UTC)

@milianw: for now I add a conflict and when libpfm4 will be updated, I'll add it as a dependency.

milianw commented on 2017-09-19 09:00 (UTC)

This package installs libpfm files, which then leads to conflicts with libpfm4. Note that the papi package doesn't install the libpfm4 headers, so it's not a full replacement for the libfpm4 package and thus breaks other packages that depend on the availability of libpfm4 and includes (like lttng-tools): error: file owned by 'libpfm4' and 'papi': 'usr/lib/libpfm.so' error: file owned by 'libpfm4' and 'papi': 'usr/lib/libpfm.so.4'