Hi Brandon, re: > I looked for binaries at > http://www.unidata.ucar.edu/downloads/ldm-mcidas/index.jsp but the link > for Linux 2.6 comes up empty. Thanks for pointing this out. re: > So, I'm trying to build ldm-mcidas > decoders on CentOS 6.5 with ldm 6.11.7 and mcidas2009o. McIDAS is > installed in /usr/local/mcidas and LDM is installed in /usr/local/ldm. > The compile seems to go ok, but when I go to a simple test, I get the > following > > address@hidden ldm-mcidas-2012]$ cd bin > address@hidden bin]$ ls > area2png batch.k lgt2md pnga2area pngg2gini proftomd uwgrid.sh > zlibg2gini > address@hidden bin]$ ./pnga2area > ./pnga2area: error while loading shared libraries: libldm.so.0: cannot > open shared object file: No such file or directory > address@hidden bin]$ ./pngg2gini > ./pngg2gini: error while loading shared libraries: libldm.so.0: cannot > open shared object file: No such file or directory This indicates that the ldm-mcidas decoders have been linked against the shared LDM library, not the static one. Setting of the LD_LIBRARY_PATH environment variable to include the directory in which the LDM shared library is installed is one way to take care of the load problem. The other approach that I favor is to link the decoders against the static LDM library. This way one does not have to muck with LD_LIBRARY_PATH. re: > The library appears to be in the right place: > address@hidden ~]$ ls /usr/local/ldm/lib > libldm.a libldm.la libldm.so libldm.so.0 libldm.so.0.0.0 I will need to update the ldm-mcidas build procedure to "burn" the location of the LDM shared library into the ldm-mcidas executables. re: > I have enclosed .bash_profile, config.log, test.log, config.status and > ldm-mcidas.log in the attached tarbundle > > Here is the details regarding our OS: > address@hidden ~]$ uname -a > Linux typhoon.plymouth.edu 2.6.32-431.20.3.el6.x86_64 #1 SMP Thu Jun 19 > 21:14:45 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux I will take a closer look at the ldm-mcidas build examples/instructions and get back to with the settings for linking statically and for "burning" the location of the LDM shared library into the executables. Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: UJW-658634 Department: Support ldm-mcidas Priority: Normal Status: Open
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.