Are you installing openmpi-dev? This package provides the symlinks for
mpicc, etc. The reason for this is that lammpi provides an alternative
mpi system. The files are renamed so that the lammpi and openmpi packages
can co-exist (providing the necessary binaries for running their
respective mpi compiled programs) and only the respective -dev package
needs to be installed when compiling new mpi programs. The fink packages
that build against either lammpi or openmpi should have a BuildDepends
on either lammpi-dev or openmpi-dev.
Jack
On Tue, Aug 18, 2009 at 02:58:31PM -0400, Alexander Hansen wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Todd Krause wrote:
> > Hi,
> >
> > I recently installed the fftw-mpi package, which in turn required
> > installation of the openmpi package (fine in my book). After finally
> > realizing that fink named the new openmpi commands in /sw/bin to have
> > "om-" prefixes, I ran make to compile the code Gadget-2, and received
> > the following error:
> >
> > 01:03 PM btpro:Gadget2> make -f
> > ../bobtodd_tests/milos_test01/makefiles/makefile.milos01
> > om-mpicc -O3 -Wall -DUNEQUALSOFTENINGS -DPEANOHILBERT -DWALLCLOCK
> > -DSYNCHRONIZATION -DISOTHERM_EQS -I/sw/include -I/sw/include
> > -I/sw/include -c -o main.o main.c
> > Cannot open configuration file
> > /sw/share/doc/openmpi/openmpi/om-mpicc-wrapper-data.txt
> > Error parsing data file om-mpicc: Not found
> > make: *** [main.o] Error 243
> > 01:03 PM btpro:Gadget2> which om-mpicc
> > /sw/bin/om-mpicc
> >
> > Interestingly, the last time I made Gadget-2, I didn't need to use
> > "om-mpicc"; simply "mpicc" seemed to find my /sw/bin/mpicc (which was
> > openmpi) without problems. Since then, unfortunately, I had to remove
> > fink and start from scratch, and this time I realized everything's
> > called "om-xxxxx". I found a similar error in an earlier exchange on
> > the fink listserve:
> >
> > http://www.opensubscriber.com/message/[email protected]/7238283.html
> >
> > the relevant part of which is the following
> >
> > -------------- begin quoted text ---------------
> > The first problem was a file which the executable needed, that had an
> > unexpected name:
> >
> > ----
> >
> > nell:~/tmp/tst barnes$ om-mpif77
> > Cannot open configuration file
> > /sw/share/doc/openmpi/openmpi/om-mpif77-wrapper-data.txt
> > Error parsing data file om-mpif77: Not found
> >
> > nell:~/tmp/tst barnes$ sudo cp
> > /sw/share/doc/openmpi/openmpi/mpif77-wrapper-data.txt
> > /sw/share/doc/openmpi/openmpi/om-mpif77-wrapper-data.txt
> >
> > nell:~/tmp/tst barnes$ ls -l /sw/share/doc/openmpi/openmpi/*77*
> > -rw-r--r-- 1 root admin 668 Jul 26 18:42
> > /sw/share/doc/openmpi/openmpi/mpif77-wrapper-data.txt
> > -rw-r--r-- 1 root admin 668 Jul 26 18:49
> > /sw/share/doc/openmpi/openmpi/om-mpif77-wrapper-data.txt
> >
> > nell:~/tmp/tst barnes$ om-mpif77
> > gfortran: no input files
> >
> > -----
> > There were many other similar .txt files which probably also need
> > renaming.
> > So that's fixed with a kludge, but now it's having trouble finding
> > libraries
> > which do exist (perhaps the same .so vs .dynlib problem?):
> >
> > /usr/bin/ld: can't locate file for: -lmpi_f77
> > collect2: ld returned 1 exit status
> > make: *** [table.x] Error 1
> >
> > -------------- end quoted text ----------------
> >
> > So my question is this: I can find the relevant data files, and I could
> > rename them all to have the "om-" prefix, but is there a better fix so
> > that I don't have to go through all that and muck around in /sw?
> > Moreover, it seems like I'll have to do that for each wrapper I use
> > (om-mpic++ next, then om-mpif77 if I have to use Fortran, etc.). And in
> > the end, even that will only get me to the library error, according to
> > the above email. Is there a resolution to this problem that I failed to
> > find?
> >
> > Thanks very much,
> > Todd
> >
> >
>
> I'll cc the maintainer for the first part.
>
> As for the the library linker issue above, it's hard to say without
> seeing what is being fed to ld. However, it may be as simple as not
> having '-L/sw/lib/openmpi' before '-lmpi_f77', since libmpi_f77.dylib is
> not in ld's default search path. How to fix this depends on what the
> package you're building supports.
> - --
> Alexander Hansen
> Fink User Liaison
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkqK+dcACgkQB8UpO3rKjQ/5/ACfZlj4yC6vQ3koohwp+a8/sjdF
> YBYAnRwM8jlk1vlNUu1ouDk51Di8LIsQ
> =8Oat
> -----END PGP SIGNATURE-----
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Fink-beginners mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.beginners
