<div>When I compile it again, there is the following error for my application code.</div>
<div>#error: can't find include file: include/finclude/petsc.h</div>
<div> </div>
<div>My application code incudes</div>
<div>#include "include/finclude/petsc.h"</div>
<div> </div>
<div>In my makefile, I set the path as follows</div>
<div>PETSC_DIR=/home/david/petsc</div>
<div>include $(PETSC_DIR)/conf/variables</div>
<div> </div>
<div>Actually there is pestc.h in the directory, how can I fix it? thanks.</div>
<div> </div>
<div>David<br></div>
<div class="gmail_quote">On Mon, Mar 22, 2010 at 6:29 PM, Satish Balay <span dir="ltr"><<a href="mailto:balay@mcs.anl.gov">balay@mcs.anl.gov</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">mpiexec is part of the MPI standard. The usage is dicated as:<br><br>mpiexec -n 2 ./pro.ex<br>
<div>
<div></div>
<div class="h5"><br>Satish<br><br>On Mon, 22 Mar 2010, David sheehan wrote:<br><br>> I tried it, but it doesn't like mpirun. For example,<br>> if I want to run<br>> mpirun -np 2 pro.ex<br>> then it would be<br>
> mpiexec -np 2 pro.ex<br>> , right? thanks.<br>><br>> David<br>><br>> On Mon, Mar 22, 2010 at 5:58 PM, Satish Balay <<a href="mailto:balay@mcs.anl.gov">balay@mcs.anl.gov</a>> wrote:<br>><br>> > As mentioned before - its 'mpiexec'<br>
> ><br>> ><br>> > Satish<br>> ><br>> ><br>> > On Mon, 22 Mar 2010, David sheehan wrote:<br>> ><br>> > > The "bin" directory has the following files:<br>> > ><br>
> > > adiforfix.py mpich2version mpiexec.poe<br>> > > parkill taucc.py<br>> > > adprocess.py mpicxx mpiexec.prun<br>> > > parseargs.py TOPSGenerator.py<br>
> > > chibaoutput mpiexec mpiexec.sshsync<br>> > > petsc_libtool TOPSInstaller.py<br>> > > configVars.py mpiexec.chiba mpiexec.uni<br>> > > petscmpiexec update.py<br>
> > > hostnames.chiba mpiexec.gmalloc mpiexec.valgrind<br>> > > popup urlget<br>> > > matlab mpiexec.lam mpif77<br>> > > portabilitycheck.py urlget.py<br>
> > > mpicc mpiexec.llrun mpif90<br>> > > processSummary.py win32fe<br>> > > which one is "mpirun"? thanks.<br>> > ><br>> > > David<br>> > ><br>
> > > On Mon, Mar 22, 2010 at 5:44 PM, Satish Balay <<a href="mailto:balay@mcs.anl.gov">balay@mcs.anl.gov</a>> wrote:<br>> > ><br>> > > ><br>> > > > You should look for mpiexec. It will be in the 'bin' dir for the<br>
> > > > prefix used - i.ed /home/david/petscdir/bin/mpiexec<br>> > > ><br>> > > > Satish<br>> > > ><br>> > > ><br>> > > > On Mon, 22 Mar 2010, David sheehan wrote:<br>
> > > ><br>> > > > > I build up petsc successfully as follows<br>> > > > > ./configure --with-cc= --prefix=/home/david/petscdir --with-cc=gcc<br>> > > > > --with-cxx=g++ --with-fc=ifort --download-mpich=1 --download-hypre=1<br>
> > > > > make<br>> > > > > make install<br>> > > > > make test<br>> > > > ><br>> > > > > Also, I can link it with my application. Now I need to run my<br>
> > application<br>> > > > > with the petsc, where can I find "mpirun" for the mpich downloaded to<br>> > run<br>> > > > my<br>> > > > > application? thanks.<br>
> > > > ><br>> > > > > David<br>> > > > ><br>> > > > ><br>> > > > ><br>> > > > > On Mon, Mar 22, 2010 at 4:45 PM, Satish Balay <<a href="mailto:balay@mcs.anl.gov">balay@mcs.anl.gov</a>><br>
> > wrote:<br>> > > > ><br>> > > > > > You can't use 2 MPIs at same time. i.e use either<br>> > --download-mpich=1<br>> > > > > > or --download-openmpi=1 - but not both.<br>
> > > > > ><br>> > > > > > Satish<br>> > > > > ><br>> > > > > > On Mon, 22 Mar 2010, David sheehan wrote:<br>> > > > > ><br>> > > > > > > You mean,<br>
> > > > > > > ./configure --with-cc=gcc --with-cxx=g++ --with-fc=ifort<br>> > > > > > --download-mpich=1<br>> > > > > > > --download-hypre=1 --download-openmpi=1<br>
> > > > > > > thanks.<br>> > > > > > ><br>> > > > > > > David<br>> > > > > > ><br>> > > > > > > On Mon, Mar 22, 2010 at 3:58 PM, Matthew Knepley <<br>
> > <a href="mailto:knepley@gmail.com">knepley@gmail.com</a>><br>> > > > > > wrote:<br>> > > > > > ><br>> > > > > > > > On Mon, Mar 22, 2010 at 3:54 PM, David sheehan <<br>
> > > > > > <a href="mailto:david.sheehanjr@gmail.com">david.sheehanjr@gmail.com</a>>wrote:<br>> > > > > > > ><br>> > > > > > > >> I don't have icc and icpc. I only have ifort and gnu compilers<br>
> > > > such<br>> > > > > > > >> g77,gcc<br>> > > > > > > >> and g++. Since my application code works very well with ifort,<br>> > can<br>> > > > I<br>
> > > > > > build<br>> > > > > > > >><br>> > > > > > > >> up PETSC plus Hypre with ifort and gnu compilers? thanks.<br>> > > > > > > >><br>
> > > > > > > ><br>> > > > > > > > It might be possible (though not guaranteed if ifort conflicts<br>> > with<br>> > > > GNU<br>> > > > > > > > somehow). You<br>
> > > > > > > > jsut provide these compilers to the configure, and use<br>> > > > > > --download-openmpi.<br>> > > > > > > ><br>> > > > > > > > Matt<br>
> > > > > > > ><br>> > > > > > > ><br>> > > > > > > >><br>> > > > > > > >> David<br>> > > > > > > >><br>
> > > > > > > >> On Mon, Mar 22, 2010 at 3:29 PM, Satish Balay <<br>> > <a href="mailto:balay@mcs.anl.gov">balay@mcs.anl.gov</a>><br>> > > > > > wrote:<br>> > > > > > > >><br>
> > > > > > > >>> If you have installation issues - send the relavent logs [in<br>> > this<br>> > > > > > case<br>> > > > > > > >>> configure.log] to petsc-maint.<br>
> > > > > > > >>><br>> > > > > > > >>> Here you appear to try too many things.. But its not clear if<br>> > you<br>> > > > are<br>> > > > > > > >>> installing openmpi/lam yourself - or using default from Red<br>
> > Hat<br>> > > > 3.4.<br>> > > > > > > >>> [note - default openmpi will be built with gnu compilers - so<br>> > > > > > > >>> unuseable from ifort].<br>
> > > > > > > >>><br>> > > > > > > >>> Thing to do:<br>> > > > > > > >>><br>> > > > > > > >>> - decide on compilers you want to use.<br>
> > > > > > > >>> - build PETSc and mpi with these compilers<br>> > > > > > > >>><br>> > > > > > > >>> [for eg: configure CC=icc CXX=icpc FC=ifort<br>
> > --download-mpich=1<br>> > > > > > > >>> --download-hypre=1]<br>> > > > > > > >>><br>> > > > > > > >>> Note: alternative f90 compilers seable on linux are gfortran,<br>
> > g95<br>> > > > > > > >>><br>> > > > > > > >>> Satish<br>> > > > > > > >>><br>> > > > > > > >>> On Mon, 22 Mar 2010, David sheehan wrote:<br>
> > > > > > > >>><br>> > > > > > > >>> > Hi,<br>> > > > > > > >>> > I am trying to compile the PETSC with hypre. I have Intel<br>
> > > > FORTRAN,<br>> > > > > > > >>> openmpi<br>> > > > > > > >>> > and lam<br>> > > > > > > >>> > MPI (gcc version 3.4.6 (Red Hat 3.4.6-3)) available.<br>
> > > > > > > >>> ><br>> > > > > > > >>> > Since my application code is in FORTRAN with dynamic memory<br>> > > > > > allocation<br>> > > > > > > >>> in<br>
> > > > > > > >>> > the code,<br>> > > > > > > >>> > so I have to use Intel FORTRAN(ifort) as the compiler to<br>> > link<br>> > > > PETSC<br>
> > > > > > > >>> with my<br>> > > > > > > >>> > application<br>> > > > > > > >>> > code. I can build up PETSC(petsc-3.0.0-p11) plus hypre with<br>
> > Lam<br>> > > > MPI<br>> > > > > > but<br>> > > > > > > >>> > without ifort<br>> > > > > > > >>> > successfully. However I can not use ifort to link the PETSC<br>
> > > > with my<br>> > > > > > > >>> > application success-<br>> > > > > > > >>> > fully. The link always shows erros about "undefined<br>
> > reference"<br>> > > > to<br>> > > > > > MPI<br>> > > > > > > >>> parts<br>> > > > > > > >>> > in my application<br>
> > > > > > > >>> > code such as 'mpi_send_', 'mpi_recv_', 'mpi_waitany_',<br>> > > > > > > >>> 'mpi_get_count_',<br>> > > > > > > >>> > and etc.<br>
> > > > > > > >>> ><br>> > > > > > > >>> > Can any one help me out? thanks in advance.<br>> > > > > > > >>> ><br>> > > > > > > >>> > Best Regards,<br>
> > > > > > > >>> ><br>> > > > > > > >>> > David<br>> > > > > > > >>> ><br>> > > > > > > >>><br>
> > > > > > > >>><br>> > > > > > > >><br>> > > > > > > ><br>> > > > > > > ><br>> > > > > > > > --<br>
> > > > > > > > What most experimenters take for granted before they begin<br>> > their<br>> > > > > > > > experiments is infinitely more interesting than any results to<br>
> > > > which<br>> > > > > > their<br>> > > > > > > > experiments lead.<br>> > > > > > > > -- Norbert Wiener<br>> > > > > > > ><br>
> > > > > > ><br>> > > > > ><br>> > > > > ><br>> > > > ><br>> > > ><br>> > > ><br>> > ><br>> ><br>> ><br>
><br><br></div></div></blockquote></div><br>