Re: PyNGL/PyNIO installation problems

Hi Ben,

To follow-up on Dave's comments about PyNGL: if you are building from source code, you can also help the PyNGL installation find libgfortran.{a,so} by setting the F2CLIBS_PREFIX environment variable.

See:

http://www.pyngl.ucar.edu/Download/build_pyngl_from_src.shtml#SetPyNGLEnvVars

for more information.

If you are installing from a precompiled binary, then Dave's suggestion should help if you already have libgfortran installed.
You might be able to find it with the "locate" command:

  locate libgfortran

If you are still having problems, then please email us with more information, like whether you're building from source or using a precompiled binary, and what kind of system you have (uname -a).

--Mary

On Sep 8, 2010, at 3:37 PM, David Brown wrote:

> I am not sure what is going on here, but it looks like there are
> different problems for PyNIO and PyNGL. Do you know if PyNIO was build
> from source or installed as a binary? This PyNIO problem looks like it
> related to the HDF4 library. Normally if the HDF4 library is build
> according to the instructions on http://www.pyngl.ucar.edu/Download/build_pynio_from_src.shtml
> it will be compiled statically. Your version seems to be linked with
> a shared version of the HDF library (called libmfhdf.so.0). It is
> possible that you could get this to work by setting LD_LIBRARY_PATH to
> the location of libmfhdf.so.0. But we always recommend that libraries
> be linked statically as much as possible.
>
> PyNGL does not seem to be able to find the gfortran library. This
> might also be fixed by setting LD_LIBRARY_PATH.
>
> Just as a general point, just because the build and install complete
> without erros, that does not necessarily indicate a successful
> install. Because the nio.so shared object is loaded dynamically, it is
> impossible to tell if the build was successful until you can import
> the module and use it. You will only have a pretty good idea the
> install was successful if you can run the test scripts.
> -dave
>
>
> On Sep 3, 2010, at 12:41 PM, Schwedler, Benjamin wrote:
>
>> A sysadmin for a cluster that I am working on has been trying to
>> install
>> PyNGL-1.3.1 and PyNIO-1.4.0. He was able to successfully build the
>> packages, but upon importing Nio and Ngl, I receive the following
>> errors:
>>
>> Python 2.5.2 (r252:60911, Apr 8 2010, 10:22:54)
>> [GCC 4.4.0] on linux2
>> Type "help", "copyright", "credits" or "license" for more information.
>>>>> import numpy
>>>>> numpy.__version__
>> '1.5.0.dev'
>>>>> import Nio
>> Traceback (most recent call last):
>> File "<stdin>", line 1, in <module>
>> File
>> "/apps/coates/Python-2.5.2/lib/python2.5/site-packages/PyNIO/Nio.py",
>> line 63, in <module>
>> from nio import *
>> ImportError: libmfhdf.so.0: cannot open shared object file: No such
>> file
>> or directory
>>>>> import Ngl
>> Traceback (most recent call last):
>> File "<stdin>", line 1, in <module>
>> File
>> "/apps/coates/Python-2.5.2/lib/python2.5/site-packages/PyNGL/Ngl.py",
>> line 38, in <module>
>> import fplib
>> ImportError:
>> /apps/coates/Python-2.5.2/lib/python2.5/site-packages/PyNGL/fplib.so:
>> undefined symbol: _gfortran_pow_r8_i4
>>
>> Builds were attempted with Python-2.5.2 with numpy-1.5.0dev and
>> Python-2.6.5 with numpy-2.0.0dev
>>
>> $ uname -a
>> Linux coates-fe02.rcac.purdue.edu 2.6.18-194.3.1.el5rcac1 #1 SMP Sun
>> May
>> 16 16:03:15 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
>>
>> Are there any suggestions for how we may able to get around this?
>> Since
>> I didn't perform the installation myself, I don't know the exact
>> versions of all libraries that were used, but I should be able to find
>> that out.
>>
>> Cheers,
>>
>> Ben
>>
>> --
>> Benjamin R. J. Schwedler
>>
>> _______________________________________________
>> pyngl-talk mailing list
>> List instructions, subscriber options, unsubscribe:
>> http://mailman.ucar.edu/mailman/listinfo/pyngl-talk
>
> _______________________________________________
> pyngl-talk mailing list
> List instructions, subscriber options, unsubscribe:
> http://mailman.ucar.edu/mailman/listinfo/pyngl-talk

_______________________________________________
pyngl-talk mailing list
List instructions, subscriber options, unsubscribe:
http://mailman.ucar.edu/mailman/listinfo/pyngl-talk
Received on Thu Sep 9 05:30:59 2010