OK - I have fixed it by including -L/opt/openmpi/lib at the very
beginning of mpicc ... -L/opt/openmpi/lib -o app.exe the rest ...
But something is wrong with dyld anyhow.
On 19 Aug 2009, at 21:04, Jody Klymak wrote:
Hi Tomek,
I'm using 10.5.7, and just went through a painful process that we
thought was library related (but it wasn't), so I'll give my less-
than-learned response, and if you sill have difficulties hopefully
others will chime in:
What is the result of "which mpicc" (or whatever you are using for
your compiling/linking? I'm pretty sure that's where the library
paths get set, and if you are calling /usr/bin/mpicc you will get
the wrong library paths in the executable.
On Aug 19, 2009, at 10:57 AM, tomek wrote:
