Discussion:
[OMPI users] configure test doesn't find cuda.h and valgrind.h for openmpi-master-201702150209-404fe32
Siegmar Gross
2017-02-15 11:46:28 UTC
Permalink
Hi,

I tried to install openmpi-master-201702150209-404fe32 on my "SUSE Linux
Enterprise Server 12.2 (x86_64)" with Sun C 5.14 and gcc-6.3.0.
Unfortunately, configure tests don't find cuda.h and valgrind.h, although
they are available. I had reported this problem already for
openmpi-master-201702080209-bc2890e.



loki openmpi-master-201702150209-404fe32-Linux.x86_64.64_cc 133 grep cuda.h
log.configure.Linux.x86_64.64_cc
checking if --with-cuda is set... found (/usr/local/cuda/include/cuda.h)
checking cuda.h usability... no
checking cuda.h presence... no
checking for cuda.h... no
checking if MPI Extension cuda has C bindings... yes (required)
checking if MPI Extension cuda has mpif.h bindings... no
checking if MPI Extension cuda has "use mpi" bindings... no
checking if MPI Extension cuda has "use mpi_f08" bindings... no

loki openmpi-master-201702150209-404fe32-Linux.x86_64.64_cc 133 grep valgrind.h
log.configure.Linux.x86_64.64_cc
checking valgrind/valgrind.h usability... yes
checking valgrind/valgrind.h presence... no
configure: WARNING: valgrind/valgrind.h: accepted by the compiler, rejected by
the preprocessor!
configure: WARNING: valgrind/valgrind.h: proceeding with the compiler's result
checking for valgrind/valgrind.h... yes


loki openmpi-master-201702150209-404fe32-Linux.x86_64.64_cc 134 cd
../openmpi-master-201702150209-404fe32-Linux.x86_64.64_gcc
loki openmpi-master-201702150209-404fe32-Linux.x86_64.64_gcc 135 grep cuda.h
log.configure.Linux.x86_64.64_gcc
checking if --with-cuda is set... found (/usr/local/cuda/include/cuda.h)
checking cuda.h usability... no
checking cuda.h presence... no
checking for cuda.h... no
checking if MPI Extension cuda has C bindings... yes (required)
checking if MPI Extension cuda has mpif.h bindings... no
checking if MPI Extension cuda has "use mpi" bindings... no
checking if MPI Extension cuda has "use mpi_f08" bindings... no

loki openmpi-master-201702150209-404fe32-Linux.x86_64.64_gcc 136 grep valgrind.h
log.configure.Linux.x86_64.64_gcc
checking valgrind/valgrind.h usability... yes
checking valgrind/valgrind.h presence... no
configure: WARNING: valgrind/valgrind.h: accepted by the compiler, rejected by
the preprocessor!
configure: WARNING: valgrind/valgrind.h: proceeding with the compiler's result
checking for valgrind/valgrind.h... yes
loki openmpi-master-201702150209-404fe32-Linux.x86_64.64_gcc 137


I would be grateful, if somebody can fix the problem. Do you need anything
else? Thank you very much for any help in advance.


Kind regards

Siegmar
Gilles Gouaillardet
2017-02-15 12:31:00 UTC
Permalink
Siegmar,

i do not think this should be fixed within Open MPI.
unlike GNU gcc, sun cc does not search in /usr/local.
so i believe it is up to the user to pass the right CPPFLAGS and LDFLAGS to
the configure command line.
if you think sun cc should search in /usr/local, then i suggest you report
this issue to Oracle


Cheers,

Gilles

On Wednesday, February 15, 2017, Siegmar Gross <
Post by Siegmar Gross
Hi,
I tried to install openmpi-master-201702150209-404fe32 on my "SUSE Linux
Enterprise Server 12.2 (x86_64)" with Sun C 5.14 and gcc-6.3.0.
Unfortunately, configure tests don't find cuda.h and valgrind.h, although
they are available. I had reported this problem already for
openmpi-master-201702080209-bc2890e.
loki openmpi-master-201702150209-404fe32-Linux.x86_64.64_cc 133 grep
cuda.h log.configure.Linux.x86_64.64_cc
checking if --with-cuda is set... found (/usr/local/cuda/include/cuda.h)
checking cuda.h usability... no
checking cuda.h presence... no
checking for cuda.h... no
checking if MPI Extension cuda has C bindings... yes (required)
checking if MPI Extension cuda has mpif.h bindings... no
checking if MPI Extension cuda has "use mpi" bindings... no
checking if MPI Extension cuda has "use mpi_f08" bindings... no
loki openmpi-master-201702150209-404fe32-Linux.x86_64.64_cc 133 grep
valgrind.h log.configure.Linux.x86_64.64_cc
checking valgrind/valgrind.h usability... yes
checking valgrind/valgrind.h presence... no
configure: WARNING: valgrind/valgrind.h: accepted by the compiler,
rejected by the preprocessor!
configure: WARNING: valgrind/valgrind.h: proceeding with the compiler's result
checking for valgrind/valgrind.h... yes
loki openmpi-master-201702150209-404fe32-Linux.x86_64.64_cc 134 cd
../openmpi-master-201702150209-404fe32-Linux.x86_64.64_gcc
loki openmpi-master-201702150209-404fe32-Linux.x86_64.64_gcc 135 grep
cuda.h log.configure.Linux.x86_64.64_gcc
checking if --with-cuda is set... found (/usr/local/cuda/include/cuda.h)
checking cuda.h usability... no
checking cuda.h presence... no
checking for cuda.h... no
checking if MPI Extension cuda has C bindings... yes (required)
checking if MPI Extension cuda has mpif.h bindings... no
checking if MPI Extension cuda has "use mpi" bindings... no
checking if MPI Extension cuda has "use mpi_f08" bindings... no
loki openmpi-master-201702150209-404fe32-Linux.x86_64.64_gcc 136 grep
valgrind.h log.configure.Linux.x86_64.64_gcc
checking valgrind/valgrind.h usability... yes
checking valgrind/valgrind.h presence... no
configure: WARNING: valgrind/valgrind.h: accepted by the compiler,
rejected by the preprocessor!
configure: WARNING: valgrind/valgrind.h: proceeding with the compiler's result
checking for valgrind/valgrind.h... yes
loki openmpi-master-201702150209-404fe32-Linux.x86_64.64_gcc 137
I would be grateful, if somebody can fix the problem. Do you need anything
else? Thank you very much for any help in advance.
Kind regards
Siegmar
_______________________________________________
users mailing list
https://rfd.newmexicoconsortium.org/mailman/listinfo/users
Jeff Squyres (jsquyres)
2017-02-15 14:10:56 UTC
Permalink
Siegmar --

Thanks for the reminder; sorry for not replying to your initial email earlier!

I just replied about the valgrind.h issue -- check out https://www.mail-archive.com/***@lists.open-mpi.org/msg30631.html.

I'm not quite sure what is going on with cuda.h, though -- I've asked Sylvain to have a look (he's the NVIDIA Open MPI rep): https://github.com/open-mpi/ompi/issues/2984.
Post by Gilles Gouaillardet
Siegmar,
i do not think this should be fixed within Open MPI.
unlike GNU gcc, sun cc does not search in /usr/local.
so i believe it is up to the user to pass the right CPPFLAGS and LDFLAGS to the configure command line.
if you think sun cc should search in /usr/local, then i suggest you report this issue to Oracle
Cheers,
Gilles
Hi,
I tried to install openmpi-master-201702150209-404fe32 on my "SUSE Linux
Enterprise Server 12.2 (x86_64)" with Sun C 5.14 and gcc-6.3.0.
Unfortunately, configure tests don't find cuda.h and valgrind.h, although
they are available. I had reported this problem already for
openmpi-master-201702080209-bc2890e.
loki openmpi-master-201702150209-404fe32-Linux.x86_64.64_cc 133 grep cuda.h log.configure.Linux.x86_64.64_cc
checking if --with-cuda is set... found (/usr/local/cuda/include/cuda.h)
checking cuda.h usability... no
checking cuda.h presence... no
checking for cuda.h... no
checking if MPI Extension cuda has C bindings... yes (required)
checking if MPI Extension cuda has mpif.h bindings... no
checking if MPI Extension cuda has "use mpi" bindings... no
checking if MPI Extension cuda has "use mpi_f08" bindings... no
loki openmpi-master-201702150209-404fe32-Linux.x86_64.64_cc 133 grep valgrind.h log.configure.Linux.x86_64.64_cc
checking valgrind/valgrind.h usability... yes
checking valgrind/valgrind.h presence... no
configure: WARNING: valgrind/valgrind.h: accepted by the compiler, rejected by the preprocessor!
configure: WARNING: valgrind/valgrind.h: proceeding with the compiler's result
checking for valgrind/valgrind.h... yes
loki openmpi-master-201702150209-404fe32-Linux.x86_64.64_cc 134 cd ../openmpi-master-201702150209-404fe32-Linux.x86_64.64_gcc
loki openmpi-master-201702150209-404fe32-Linux.x86_64.64_gcc 135 grep cuda.h log.configure.Linux.x86_64.64_gcc
checking if --with-cuda is set... found (/usr/local/cuda/include/cuda.h)
checking cuda.h usability... no
checking cuda.h presence... no
checking for cuda.h... no
checking if MPI Extension cuda has C bindings... yes (required)
checking if MPI Extension cuda has mpif.h bindings... no
checking if MPI Extension cuda has "use mpi" bindings... no
checking if MPI Extension cuda has "use mpi_f08" bindings... no
loki openmpi-master-201702150209-404fe32-Linux.x86_64.64_gcc 136 grep valgrind.h log.configure.Linux.x86_64.64_gcc
checking valgrind/valgrind.h usability... yes
checking valgrind/valgrind.h presence... no
configure: WARNING: valgrind/valgrind.h: accepted by the compiler, rejected by the preprocessor!
configure: WARNING: valgrind/valgrind.h: proceeding with the compiler's result
checking for valgrind/valgrind.h... yes
loki openmpi-master-201702150209-404fe32-Linux.x86_64.64_gcc 137
I would be grateful, if somebody can fix the problem. Do you need anything
else? Thank you very much for any help in advance.
Kind regards
Siegmar
_______________________________________________
users mailing list
https://rfd.newmexicoconsortium.org/mailman/listinfo/users
_______________________________________________
users mailing list
https://rfd.newmexicoconsortium.org/mailman/listinfo/users
--
Jeff Squyres
***@cisco.com
Loading...