On Tue, Oct 4, 2011 at 3:15 PM, Barry Smith <span dir="ltr"><<a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Are you using the PETSc makefiles to compile it? Or did you make up that compile line yourself? Why not just use the PETSc makefile to compile it?<br>
<br>
Presumably cusp/thrust has some pattern for what include files need to be included in what order. If you do not know the pattern then why not start by copying what PETSc does, since that compiles? For example<br>
cuspvecimpl.h has<br>
<br>
#include <cublas.h><br>
#include <cusp/blas.h><br>
#include <thrust/device_vector.h><br>
#include <thrust/iterator/constant_iterator.h><br>
#include <thrust/transform.h><br>
#include <thrust/iterator/permutation_iterator.h><br>
<br>
while cuspmatimpl.h has<br>
<br>
#include <../src/vec/vec/impls/seq/seqcusp/cuspvecimpl.h><br>
#include <cusp/csr_matrix.h><br>
#include <cusp/multiply.h><br>
/*for MatCreateSeqAIJCUSPFromTriple*/<br>
#include <cusp/coo_matrix.h><br>
<br>
so start with at least those. Generally just picking a couple of random include files from some C++ package (like cusp/thrust) and including them won't work.</blockquote><div><br></div><div>I believe that your problem is the clash of VecType between CUSP and PETSc. In <a href="http://aijcusp.cu">aijcusp.cu</a>, we have</div>
<div><br></div><div><div>#undef VecType</div><div>#include "../src/mat/impls/aij/seq/seqcusp/cuspmatimpl.h"</div></div><div><br></div><div> Matt</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<font color="#888888"><br>
Barry<br>
</font><div><div></div><div class="h5"><br>
<br>
On Oct 4, 2011, at 2:07 PM, Shiyuan wrote:<br>
<br>
> Hi,<br>
> I cannot compiling a source file with petsc.h and cusp headers like the following:<br>
><br>
> #include"petsc.h"<br>
> #include<iostream><br>
> #include "cusp/csr_matrix.h"<br>
> #include <cusp/krylov/cg.h><br>
> int main(void){<br>
> std::cout<<"Hello World!"<<std::endl;<br>
> return 0;<br>
> }<br>
><br>
> I use the following to compile it:<br>
><br>
> nvcc -m64 -O -arch=sm_13 -c --compiler-options="-Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -O -I/home/guest/sgu1/softwares/petsc-dev/include -I/home/guest/sgu1/softwares/petsc-dev/helena-cxx-nompi-os64-release/include -I/usr/local/cuda/include -I/home/guest/sgu1/softwares/cusp-library/ -I/home/guest/sgu1/softwares/thrust/ -I/home/guest/sgu1/softwares/petsc-dev/include/mpiuni -DCUDA=1 -I/home/guest/sgu1/softwares/slepc-dev -I/home/guest/sgu1/softwares/slepc-dev/helena-cxx-nompi-os64-release/include -I/home/guest/sgu1/softwares/slepc-dev/include -I/home/guest/sgu1/softwares/ImageMagick-6.7.2/include/ImageMagick -D__INSDIR__= -I/home/guest/sgu1/softwares/slepc-dev -I/home/guest/sgu1/softwares/slepc-dev/helena-cxx-nompi-os64-release/include -I/home/guest/sgu1/softwares/slepc-dev/include" MyKspTmp4.cu -o MyKspTmp4.o<br>
><br>
> and it gives me error:<br>
> /usr/local/cuda/include/thrust/detail/device/cuda/detail/b40c/vector_types.h(37): error: expected an identifier<br>
><br>
> I think I did not do it in a correct way. I took a a look at some of petsc's .cu files, they usually include a long list of headers. Can petsc.h directly included in a source code with cusp headers? What's the correct way to do it? Does the makefile system in petsc provide the command or flags to do that? How can I obtain those flags?<br>
><br>
> And after I compile it and obtain .o files, can I use g++ to link the .o files with petcs libs and other .o files as usual, i.e.,<br>
> g++ -o $(BIN_DIR)/$@ $(CPPFLAGS) $@.s $(objects) $(PETSC_LIB) $(OTHERS)<br>
> or I need to do some extra steps and some specific linking flags to do that?<br>
> Thanks.<br>
><br>
> Shiyuan<br>
><br>
><br>
><br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>
-- Norbert Wiener<br>