Search Criteria
Package Details: extrae 4.2.3.20240910-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/extrae.git (read-only, click to copy) |
---|---|
Package Base: | extrae |
Description: | Instrumentation framework to generate execution traces of the most used parallel runtimes (from BSC). |
Upstream URL: | https://www.bsc.es/discover-bsc/organisation/scientific-structure/performance-tools |
Licenses: | LGPL2.1 |
Submitter: | gamezelda |
Maintainer: | gamezelda |
Last Packager: | gamezelda |
Votes: | 1 |
Popularity: | 0.000000 |
First Submitted: | 2019-02-28 22:36 (UTC) |
Last Updated: | 2024-09-10 19:41 (UTC) |
Dependencies (6)
- libunwind (libunwind-carbonAUR, libunwind-gitAUR)
- libxml2 (libxml2-gitAUR, libxml2-2.9AUR)
- openmpi (openmpi-gitAUR)
- papiAUR (papi-cudaAUR)
- python (python37AUR, python311AUR, python310AUR)
- zlib (zlib-ng-compat-gitAUR, zlib-gitAUR, zlib-ng-compat)
Latest Comments
gamezelda commented on 2022-05-21 15:37 (UTC)
Arch's openmpi 4.1.3-1 package (currently in testing) causes a conflict with extrae 4.0.1.20220513-1 due to both libraries installing a libompitrace library. I've updated extrae to rename extrae's version to libextraeompitrace to avoid the conflict.
If you hit the conflict, try to upgrade extrae before openmpi.
gamezelda commented on 2022-02-22 00:48 (UTC) (edited on 2022-04-12 21:59 (UTC) by gamezelda)
Looks like the build broke with the recent gcc+binutils upgrade, seems similar to https://bugs.archlinux.org/task/40174. For now as a workaround, you can downgrade gcc and binutils down to those versions in order to build the package:
EDIT: Opened https://bugs.archlinux.org/task/73928
EDIT: Should be fixed in the next binutils release from Arch.
EDIT: Fixed in binutils 2.38-4
gamezelda commented on 2020-10-08 01:10 (UTC) (edited on 2020-10-08 02:37 (UTC) by gamezelda)
@teleportex: I have an idea what may have happened... do you happen to have /bin before or instead of /usr/bin in your PATH for some reason? I'd be nice if you could check if running "which xml2-config" on the console returns "/bin/xml2-config" for you (rather than "/usr/bin/xml2-config" which is what it normally does for me).
Long short history, I found some code that tries to guess where the libxml2 includes folder is relative to the xml2-config binary, but it's pretty fragile and breaks if it finds xml2-config in /bin instead of /usr/bin... if I put /bin before or instead of /usr/bin in my PATH I can reproduce the same behaviour I think you're seeing, where the configure script completes successfully, but during the compilation process libxml/xmlmemory.h is not found since the libxml2 includes path given to GCC is wrong.
Even with this weird PATH config., I'm inclined to believe it should work anyway and it's really some problem with extrae's libxml2 detect logic rather... I'll likely just put that --with-xml-prefix flag you found as a workaround. Anyway, if that's the problem, it'd be probably a wise option for you to use /usr/bin instead of /bin your PATH since that's Arch's default and maybe other things will break sooner or later.
EDIT: I added the --with-xml-prefix flag to the PKGBUILD, also to clusteringsuite's PKGBUILD which had the same problem.
gamezelda commented on 2020-10-07 09:29 (UTC)
@teleportex: Hmmm, not sure what can be going on there since it built for me a few days ago on a clear container, but at the same time I know some of those BSC packages don't autodetect libraries in /usr too well. I'll take a look later.
Glad the BSC packages were useful :)
teleportex commented on 2020-10-07 06:54 (UTC) (edited on 2020-10-07 06:55 (UTC) by teleportex)
I've got an error that xmlmemory.h header was not found. I took a look into the Makefile generated by the configure and found that the include line to the libxml2 headers was
-I//include/libxml2
looked at configure options and figured out that we were needing to tell the configure where to find libxml and it is installed in /usr.Fixed it by adding to the PKGBUILD configure line the flag:
Also... Thanks for all BSC packages! ;)
gamezelda commented on 2019-02-28 22:42 (UTC)
The package has many configuration switches to link against more or less dependencies, for the time being I have added as dependencies the ones the ./configure script complains about (which seem interesting). Suggestions welcome.