Subject: Re: [nmr_sparky] 64-bit Linux Sparky
From: Hinck, Andrew Peterson
Date: Aug 7, 2014

Previous: 931 Next: 933


We downloaded and installed on our 64-bit CentOS 6 system ... it runs without making any additional adjustments.

Andy

On Aug 6, 2014, at 3:13 PM, Tom Goddard goddard@... [nmr_sparky] nmr_sparky@yahoogroups.com wrote:

I compiled a 64-bit Linux version of Sparky and put it on the Sparky web site



It is compiled with a very old 64-bit Debian 4 Linux in an attempt to make it compatible with as many linux distributions as possible. I tested it on a recent Ubuntu distribution and found I had to install csh (C shell) but then Sparky ran fine.

Tom


On Aug 6, 2014, at 7:11 AM, Fowler, Andrew andrew-fowler@... [nmr_sparky] nmr_sparky@yahoogroups.com wrote:


Since the 32-bit library issue seems to pop up more and more, I’m replying to this. FWIW, this isn’t limited at all to Sparky, I run into it semi-regularly.

The firs thing I do with any 64-bit Linux installed, at least on any of the RedHat-based distributions, is “yum install *compat*” which should give you a lot of the 32-bit libraries and headers. I also manually add 32-bit versions of some common ones like libjpeg, libtiff, and zlib.

In this particular case, the Sparky-included shared object (i.e. library) spy.so is complaining. So, a quick Google search to find out how to see what a library depends on comes up with the “readelf” command (output truncated after the dependencies). Everything listed needs to be installed and available.

[afowler@rose sparky]$ readelf -d /usr/local/sparky/python/sparky/spy.so

Dynamic section at offset 0x190184 contains 28 entries:
Tag Type Name/Value
0x00000001 (NEEDED) Shared library: [libtk8.4.so]
0x00000001 (NEEDED) Shared library: [libtcl8.4.so]
0x00000001 (NEEDED) Shared library: [libX11.so.6]
0x00000001 (NEEDED) Shared library: [libdl.so.2]
0x00000001 (NEEDED) Shared library: [libstdc.so.6]
0x00000001 (NEEDED) Shared library: [libm.so.6]
0x00000001 (NEEDED) Shared library: [libgcc_s.so.1]
0x00000001 (NEEDED) Shared library: [libc.so.6]

Finally, if you aren’t sure what package contains that library, you can use yum whatprovides” to try and find it. As a rule, I like to make sure I have the third party repositories set up in yum as well (rpmfusion for Fedora, epel for CentOS). Just choosing libdl.so.2 as an example because it doesn’t ring a bell for me (make sure you use the FULL library name), we find you need to have the glibc package installed:

[afowler@rose ~]$ yum whatprovides libdl.so.2
Loaded plugins: langpacks, refresh-packagekit
glibc-2.17-4.fc19.i686 : The GNU libc libraries
Repo : fedora
Matched from:
Provides : libdl.so.2

If that doesn’t work, I’m afraid you’ll need to head over to Google and search for what you need. I like to make sure I search for the package name Linux version.

Hope this saves someone some time and effort.

Cheers,

Andrew



Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you.