On May 29, 2007, at 7:35 AM, Jack Howarth wrote:
and if you see environ undefined, identify which library
it is in and which object file it came from. I would also
note that my patch reveals that several instances of the
environ variable being declared that are missing the Windows
wrappers. So i
Ralph,
I don't know why such patches should be harder to
maintain in Windows than on Darwin. All you do is
the equivalent to...
cd /sw/lib/openmpi/lib
nm * | grep environ
and if you see environ undefined, identify which library
it is in and which object file it came from. I would also
note th
Brian,
Below is the response I got from the fink developer
who was trying to package paraview and ran into this
problem with the undefined environ symbol in openmpi.
I have also emailed on darwin-dev to get a clarification
on this issue. However your argument against target
specific chances is
I am no expert on this issue. However, having watched those attempting to
maintain the Windows port using the same approach you are advocating, I can
say that requiring APPLE-specific "if...include" logic almost certainly will
be an exercise in frustration, if not futility. Many of us actually deve
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
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
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
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
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
