Good! Sent from my PDA. No type good.
On Oct 8, 2010, at 2:34 PM, "Richard Walsh" <richard.wa...@csi.cuny.edu> wrote: > > All, > > Regarding building HD5 ... the OpenMPI 1.4.1 wrapper using the May 2010 > release of the Intel Compiler Toolkit Cluster Edition (ICTCE) worked for me. > Here is my config.log header: > > $ ./configure CC=mpicc CXX=mpiCC F77=mpif77 FC=mpif90 --enable-parallel > --prefix=/share/apps/hdf5/1.8.4p --with-zlib=/share/apps/zlib/1.2.3/lib > --with-szlib=/share/apps/szip/2.1/lib --disable-shared > > With some tweaking I was able to build the whole WRF and NCAR-NCL > stack here. > > Regards, > > rbw > > Richard Walsh > Parallel Applications and Systems Manager > CUNY HPC Center, Staten Island, NY > 718-982-3319 > 612-382-4620 > > Reason does give the heart pause; > As the heart gives reason fits. > > Yet, to live where reason always rules; > Is to kill one's heart with wits. > ________________________________________ > From: users-boun...@open-mpi.org [users-boun...@open-mpi.org] On Behalf Of > Gus Correa [g...@ldeo.columbia.edu] > Sent: Friday, October 08, 2010 1:58 PM > To: Open MPI Users > Subject: Re: [OMPI users] hdf5 build error using openmpi and Intel Fortran > > Jeff Squyres wrote: >> On Oct 8, 2010, at 1:00 PM, Götz Waschk wrote: >> >>> I have solved this problem myself. The trick is not to use the >>> compiler wrappers but icc and ifort directly. But in that case you'll >>> have to link to libmpi_f77 manually and set the variable RUNPARALLEL >>> to a working mpirun command. >> >> Strange. >> >> Be sure to see: >> http://www.open-mpi.org/faq/?category=mpi-apps#cant-use-wrappers >> > Hi Jeff > > Sadly, it is not only HDF5. > > There are several public domain parallel programs which we use here > that refuse to build using the mpi wrappers (from OpenMPI, > MPICH2, or MVAPICH2), and require the same "deconstruction" > of configuration and make files that Gotz probably had to face. > > Typically the Makefiles have hardwired items that cannot be overridden > (e.g. -lmpich for the MPI library name passed to the linker, > compiler options and flags that are vendor-specific, logic that > separates MPI, OpenMP, and serial compilation, etc). > I have used the FAQ link you sent many times in this regard. > > I would guess that even more than the end users of MPI, > it is the developers of public domain software > (and of software projects funded by public grants) > who need to be convinced that the right thing > to do is to ensure that MPI wrappers will compile their > software without problems. > > My $0.02 > Gus Correa > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users > > Think green before you print this email. > > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users
