Thomas Gruber

I released LIKWID 5.2.1 some time ago but did not add a new PR here because there were still two open. There have been **three** releases since I opened this...

Hi. I'm having a similar problem and while c-for-go recognizes that it is an `uint64_t` after adding the right header, it still uses `uint32` on the Golang side: ```go func...

My remark is related to this sentence part: > You should try editing your /usr/local/include/stddef.h file or wherever that uint64_t type is defined [...]

@carstenbauer: The `ldd --version` call is used to determine the glibc version because old glibc version lack the wrappers for `sched_setaffinity`. You can just add `-DHAS_SCHEDAFFINITY` to the `DEFINES` to...

> Can you elaborate a bit more, i.e. where should I add it exactly? I tried setting it in make/config_defines.mk (and make/include_GCC.mk / make/include_GCCX86.mk) without success. If you add it...

> Why isn't the easyconfig patch the default? I.e., is there a deeper reason for the creation of libhwloc.so.5.2? @carstenbauer: I test LIKWID only in the default configuration varying important...

> The script bin/likwid-topology(and probably also the others) hardcodes local absolute paths of the build environment, which won't exist at runtime. That's not going to work. @giordano This can be...

I'm in the progress of making LIKWID relocatable but it's not finished yet: https://github.com/RRZE-HPC/likwid/pull/480

Other feature requests concerning likwid-mpirun: 1. Support for the colon syntax: `mpirun -n 1 ./a.out : -n 1 ./a.out` 2. Fix problems if "--" on cmdline but not meant for...

We would be open for a persistent access daemon as long as it is configurable. I would say, either you use a persistent daemon or the current method to start...