Thanks a lot.
It worked very nicely for me.
On Tue, Apr 3, 2018 at 12:54 PM, Gilles Gouaillardet
wrote:
> In that case, you need to
>
> configure --with-cuda=/usr/local/cuda-8.0
>
>
> Cheers,
>
>
> Gilles
>
>
> On 4/3/2018 4:12 PM, abhisek Mondal wrote:
>
>> I have cuda installed in /usr/local/c
In that case, you need to
configure --with-cuda=/usr/local/cuda-8.0
Cheers,
Gilles
On 4/3/2018 4:12 PM, abhisek Mondal wrote:
I have cuda installed in /usr/local/cuda-8.0.
On Tue, Apr 3, 2018 at 12:37 PM, Gilles Gouaillardet
mailto:gil...@rist.or.jp>> wrote:
Did you install CUDA an
I have cuda installed in /usr/local/cuda-8.0.
On Tue, Apr 3, 2018 at 12:37 PM, Gilles Gouaillardet
wrote:
> Did you install CUDA and where ?
>
>
> On 4/3/2018 3:51 PM, abhisek Mondal wrote:
>
>> Thanks a lot. Installing the headers worked like a charm !
>>
>> I have a question though. Why does c
Did you install CUDA and where ?
On 4/3/2018 3:51 PM, abhisek Mondal wrote:
Thanks a lot. Installing the headers worked like a charm !
I have a question though. Why does configuration says:
Version: 3.0.1
Build MPI C bindings: yes
Build MPI C++ bindings (deprecated): no
Build MPI Fortran bin
Thanks a lot. Installing the headers worked like a charm !
I have a question though. Why does configuration says:
Version: 3.0.1
Build MPI C bindings: yes
Build MPI C++ bindings (deprecated): no
Build MPI Fortran bindings: mpif.h, use mpi
MPI Build Java bindings (experimental): no
Build Open SHM
It looks like kernel-headers is required too
Cheers,
Gilles
On 4/3/2018 2:28 PM, abhisek Mondal wrote:
Hello,
Installing glibc moved the installation little bit but again stuck at
sanity check.
Location of config.log:
https://drive.google.com/drive/u/0/folders/0B6O-L5Y7BiGJfmQ4N2FpblBEcF
Hello,
Installing glibc moved the installation little bit but again stuck at
sanity check.
Location of config.log:
https://drive.google.com/drive/u/0/folders/0B6O-L5Y7BiGJfmQ4N2FpblBEcFNxaDZnaGpsUFFEUlotVWFjajR0UFFHNk5aYlhoSHVTWkU
$ cpp --version
cpp (GCC) 4.8.5 20150623 (Red Hat 4.8.5-16)
Copyri
This is the relevant part related to this error
configure:6620: checking whether we are cross compiling
configure:6628: gcc -o conftest conftest.c >&5
conftest.c:10:19: fatal error: stdio.h: No such file or directory
#include
^
compilation terminated.
configure:6632: $? =
To be accurate, the error is:
[root@localhost build]# ../configure --prefix=/usr/local/openmpi-3.0
checking for perl... perl
== Configuring Open MPI
===
Actually this error is happening for both versions. I tried to build
openmpi-2.0 and openmpi-3.0.
On Tue, Apr 3, 2018 at 9:48 AM, Douglas L Reeder
wrote:
> In the boldface line it refers to an openmpi-2.0.4 installation. It
> appears that the 3.0 build is trying to use libraires or includes from
Hello,
I have uploaded the config.log here:
https://drive.google.com/drive/u/0/folders/0B6O-L5Y7BiGJfmQ4N2FpblBEcFNxaDZnaGpsUFFEUlotVWFjajR0UFFHNk5aYlhoSHVTWkU
On Tue, Apr 3, 2018 at 9:47 AM, Gilles Gouaillardet
wrote:
> Can you please compress and attach your config.log ?
>
>
> You might al
In the boldface line it refers to an openmpi-2.0.4 installation. It appears
that the 3.0 build is trying to use libraires or includes from the 2.04 install
instead of the 3.0 build. Can you carefully define your PATH and
LD_LIBRARY_PATH (or whatever linux calls it) to prevent the 3.0 build from
Can you please compress and attach your config.log ?
You might also want to double check you can compile *and* run a simple C
hello world program
Cheers,
Gilles
On 4/3/2018 1:06 PM, abhisek Mondal wrote:
Hi,
I need some help regarding compiling Openmpi-3.0. I have perfectly
working C
13 matches
Mail list logo
