Hello all
I downloaded some code samples from here:
https://github.com/parallel-forall/code-samples/
and tried to build the subdirectory
posts/cuda-aware-mpi-example/src
in my CentOS 7 machine.
I had to make several changes to the Makefile before it would build. The
modified Makefile is attac
Durga,
The Cuda libraries use the C++ std libraries. That's the std::ios_base
errors.. You need the C++ linker to bring those in.
Damien
On March 20, 2016 9:15:47 AM "dpchoudh ." wrote:
Hello all
I downloaded some code samples from here:
https://github.com/parallel-forall/code-samples/
I am a bit puzzled...
if only cuda uses the c++ std libraries, then it should depend on them
(ldd libcudaxyz.so can be used to confirm that)
and then linking with cuda lib should pull the c++ libs
could there be a version issue ?
e.g. the missing symbol is not provided by the version of the c++ l
According to the error message, "device.o" is the file that causes the error.
According to the source code to which you point, this file is
generated from a Cuda file, not from a C file. Cuda is close to C++,
and apparently nvcc makes use of C++ features. Thus you need the C++
run-time libraries.
I'd tend to agree with Gilles. I have written CUDA programs in pure C (i.e.
neither involving MPI nor C++) and a pure C based tool chain builds the
code successfully. So I don't see why CUDA should be intrinsically C++.
>From the Makefile (that I had attached in my previous mail) the only CUDA
lib
Dear Xavier,
Yes, I did. I followed the instructions available in that file, especially
at sub-section 4.1.
I configured boot-strap IP using the ./configure options.
in front-end node, the boot-strap IP is its IP address because I want to
make it as an ftb_database_server.
in every compute nodes,
