| Summary: | dev-libs/papi - ? | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Phil Tooley <phil.tooley> |
| Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 506276 | ||
| Attachments: | fixed papi 5.5.1 ebuild | ||
Comment on attachment 581944 [details]
fixed papi 5.5.1 ebuild
--- a/papi-5.5.1.ebuild
+++ b/papi-5.5.1.ebuild
@@ -28,6 +28,7 @@
--with-shlib
--with-perf-events
--with-pfm-prefix="${EPREFIX}/usr"
+ --with-pfm-libdir="${EPREFIX}/usr/lib64"
)
autotools-utils_src_configure
}
Um, what if your LIBDIR happens to be something other than "lib64"?
Please attach the entire failing build log to this bug report.
|
Created attachment 581944 [details] fixed papi 5.5.1 ebuild By default PAPI assumes that libpfm.a is found in ${EPREFIX}/usr/lib, which is no longer the case following the removal of this symlink in the 17.1 profile. Fix is to provide --with-pfm-libdir="${EPREFIX}/usr/lib64" as in attached ebuild. I have only attached the one ebuild as example but this bug appears to affect all versions in portage.