Thanks for the replies again,
i found though that the directory bmake/{PETSC_ARCH} included the files (i.e.
petscconf.h) that it couldn't find before.
So now it seems that it works.
I am not sure how i was supposed to use PETsC makefiles when i already have a
existing code into which i try
I recommend reading the makefile section of the manual. Briefly, you should
at least use the bmake/common/variables makefile to get such things as
PETSC_INCLUDE correct (that is the problem here), if not use the targets in
bmake/common/rules. You could use our example makefiles as a guide.
On Thu, 1 Jun 2006, Satish Balay wrote:
Looks like you are not using PETSc makefiles. This is the recommended
thing to do.
I intend to say 'The recommended method is to use PETSc makefiles'.
Satish
Thanks for the replies,
the whole mpicc is a little system specific. It build the libraries after all,
so it's fine.
However, now i got another question. I link the libraries into my program, and
then in my top level code i include petscksp.h. When i try to compile it, it
gives me the
Hi,
i need to build PETsC on s sycld machine. Basically i need to have MPI support
in PetsC but i need to switch from using mpicc to gcc.
I was wondering if someone could point to how i can do that. (Is there an
option that i overlooked?)
thanks
mat
You can have PETSc install MPI using --download-mpich. You can make
sure that it does not use mpicc using --with-mpi-compilers=0.
Matt
On 5/31/06, Matt Funk mafunk at nmsu.edu wrote:
Hi,
i need to build PETsC on s sycld machine. Basically i need to have MPI
support
in PetsC but i need
On Wed, 31 May 2006, Matt Funk wrote:
Hi,
i need to build PETsC on s sycld machine. Basically i need to have MPI
support
in PetsC but i need to switch from using mpicc to gcc.
why use gcc over mpicc? [mpicc should be internally using gcc so it
should satisfy the gcc requiremetn]
I was
