make and install bug

[icurry]

HI, there:

i was installing papi-6.0.0, however i encounter the following error while the 'make && make install' command:

make -C ctests
make[1]: Entering directory '/papi-6.0.0/src/ctests'
mpicc -I../testlib -I../validation_tests -I.. -I.  -g -diag-disable 188,869,271  -O1  mpi_hl.c ../testlib/libtestlib.a ../testlib/do_loops.o ../libpapi.a  -o mpi_hl
gcc: error: 188,869,271: No such file or directory
Makefile.recipies:243: recipe for target 'mpi_hl' failed
make[1]: *** [mpi_hl] Error 1
make[1]: Leaving directory '/papi-6.0.0/src/ctests'
Makefile.inc:244: recipe for target 'ctests' failed
make: *** [ctests] Error 2

Looking forward for your help!

Sincerely,

[Frank Winkler]

Hi,

Are you using icc? If so, please type “mpicc --version”. It looks like mpicc is using gcc.
Can you unload the mpi module that mpicc is not detected?

If this does not solve the problem, please use the bug report guidelines here:
https://bitbucket.org/icl/papi/wiki/PAPI-Bug-Report.md
and send us the required details.

Thanks,
Frank

[icurry]

Hi, Frank:

yes, i was using icc (ICC) 19.1.1.217 20200306

i get "gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0" after typing "mpicc --version"

in the src/ctest dir, you can find mpi_hl.c & mpi_omp_hl.c & first.c.

i changed mpicc to mpiicc, the installation passed.

however, it seemed the mpi module faile to install:

I../testlib -I../validation_tests -I.. -I. -g -diag-disable 188,869,271 -O1 mpi_hl.c ../testlib/libtestlib.a ../testlib/do_loops.o ../libpapi.a -o mpi_hl make[2]: I../testlib: Command not found Makefile.recipies:243: recipe for target 'mpi_hl' failed make[2]: [mpi_hl] Error 127 (ignored) I../testlib -I../validation_tests -I.. -I. -qopenmp -g -diag-disable 188,869,271 -O1 mpi_omp_hl.c ../testlib/libtestlib.a ../testlib/do_loops.o ../libpapi.a -o mpi_omp_hl make[2]: I../testlib: Command not found Makefile.recipies:246: recipe for target 'mpi_omp_hl' failed make[2]: [mpi_omp_hl] Error 127 (ignored) I../testlib -I../validation_tests -I.. -I. -g -diag-disable 188,869,271 -O1 first.c ../testlib/libtestlib.a ../testlib/do_loops.o ../libpapi.a -o mpifirst make[2]: I../testlib: Command not found Makefile.recipies:249: recipe for target 'mpifirst' failed make[2]: [mpifirst] Error 127 (ignored)

other information you may need:

$ uname -a Linux ubuntu1804 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ cat /proc/cpuinfo | grep "name" | head -n 1 model name : Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz $ gcc --version gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0

$ papi_version PAPI Version: 5.6.0.0 $ papi_component_avail Available components and hardware information.

[Frank Winkler]

Hi,

First of all it should be ensured that an old PAPI is removed from the system or is not accessible. If you want to use icc, mpicc should use icc as well.

For example:

mpicc --version
icc (ICC) 19.0.5.281 20190815

PAPI only builds the mpi examples if mpicc is available.

If you unload the mpi module (so PAPI cannot find mpicc) it should work.

The output you sent me is not very helpful. Where and how did you replace mpicc with mpiicc?

Best,

Frank

[icurry]

it is at src/ctest/Makefile.recipe

[Frank Winkler]

Hi,

Well, you could also remove the three MPI tests from the Makefile.recipe.
vi papi-6.0.0.1/src/ctests/Makefile.recipies
12 #MPI = mpi_hl mpi_omp_hl \
13 # mpifirst

If this does not work, I need more detailed information, for example your configure setting, see instructions: https://bitbucket.org/icl/papi/wiki/PAPI-Bug-Report.md.

It is also confusing. You said the installation passed and then you sent me compile errors which do not show the whole commands due to “make -j”.

I guess you want to install PAPI on your own machine. You should try the latest Bug Fix release https://bitbucket.org/icl/papi/wiki/PAPI-Releases.md and follow the example that is described here:

https://bitbucket.org/icl/papi/wiki/Downloading-and-Installing-PAPI.md

Best,

Frank

[Frank Winkler]

Hi,

This issue is fixed now. Please let us know if it works for you that we can close this issue.

You need to install the latest repo version, see above.

Best,
Frank

[icurry]

yes, it works for now and you can close it. many thanks!