On MacOS X, the current v1.1.5 and v1.2.2 sources for openmpi
create shared libraries with undefined environ symbols. This
problem on MacOS X and the available workarounds are discussed
on the fink wiki section on Porting Notes...
http://wiki.finkproject.org/index.php/Fink:Porting_Notes
There
On May 28, 2007, at 10:59 AM, Jack Howarth wrote:
On MacOS X, the current v1.1.5 and v1.2.2 sources for openmpi
create shared libraries with undefined environ symbols. This
problem on MacOS X and the available workarounds are discussed
on the fink wiki section on Porting Notes...
I understa
I have been told that Paraview is one package that
exhibits this problem with undefined environ symbols.
This will occur in any package which creates its own
shared libraries that link in any openmpi shared library
that contains the undefined environ symbol. I think it
is unreasonably restrictiv
The following patch, against openmpi v1.1.5, prevents undefined environ symbols
in the openmpi shared libraries
on MacOS X. This approach avoids the need to modifiy the configure scripts.
Jack
diff -uNr openmpi-1.1.5/ompi/communicator/comm_dyn.c
openmpi-1.1.5.environ/ompi
The following patch, against openmpi v1.2.2, prevents undefined environ symbols
in the openmpi shared libraries
on MacOS X. This approach avoids the need to modifiy the configure scripts.
Jack
diff -uNr openmpi-1.2.2/ompi/communicator/comm_dyn.c
openmpi-1.2.2.environ/omp
On May 28, 2007, at 4:57 PM, Jack Howarth wrote:
I have been told that Paraview is one package that
exhibits this problem with undefined environ symbols.
This will occur in any package which creates its own
shared libraries that link in any openmpi shared library
that contains the undefined e
This is the previous patch for 1.2.2 again with a minor typo fixed.
One of the ifdef's was missing an underscore.
Jack
diff -uNr openmpi-1.2.2/ompi/communicator/comm_dyn.c
openmpi-1.2.2.environ/ompi/communicator/comm_dyn.c
--- openmpi-1.2.2/ompi/communicator/comm_dyn.c 20
Brian,
If you Google "crt_externs.h darwin", you will see that this approach
is very widely used for many packages include wine, 4Suite, ruby, etc.
We can take this over to the darwin developer mailing list but they
will tell you the same thing I am. It is bad form to create shared
libraries wi
Brian,
One general example of why openmpi shouldn't be creating
shared libraries with undefined environ symbols is as follows.
If a python based application was using the openmpi shared libraries
linked into the application's python module, your suggested
approach would be unusable since the us
