xmgrace problem

[centguy]

Just did yum update

Linux centos60-fuj 2.6.32-71.29.1.el6.x86_64 #1 SMP Mon Jun 27 19:49:27 BST 2011 x86_64 x86_64 x86_64 GNU/Linux


(1) yum install grace
is successful, but then

xmgrace
xmgrace: error while loading shared libraries: libhdf5_hl.so.6: cannot open shared object file: No such file or directory

EVEN though
[root@centos60-fuj grace-5.1.20]# yum install libhdf5_hl.so.6
Loaded plugins: fastestmirror, refresh-packagekit
Loading mirror speeds from cached hostfile
* base: mirror.averse.net
* epel: ftp.cuhk.edu.hk
* extras: mirror.averse.net
* rpmforge: fr2.rpmfind.net
* updates: mirror.averse.net
Setting up Install Process
Package hdf5-1.8.5.patch1-5.el6.i686 already installed and latest version
Nothing to do

(2) to install from source,

./configure says

checking for X... no

so the GUI xmgrace cannot be generated.

Conclusion: I don't know what to do !

[TrevorH]

Sounds like you have grace for x86_64 but only the ix86 version of the library installed.

[centguy]

I solved this by

yum install hdf5

however, this provides only libhdf5.so.7 and libhdf5_hl.so.7


Using ldd command is to find out what are needed and followed by

cp libhdf5.so.7 libhdf5.so.6
cp libhdf5_hl.so.7 libhdf5_hl.so.6

to work.

[pschaff]

Did you install grace from EPEL? Your hdf5 is from a source other than EPEL whose version provides the "6" files you copied to, but not the "7" versions.

[centguy]

Thanks for asking. I was able to install grace as I have said earlier but then I removed it due to some conflict when I click on Software Update. After that, I cannot yum install grace anymore.

I hit:

[quote]
[root@centos60-fuj ~]# uname -a
Linux centos60-fuj 2.6.32-71.29.1.el6.x86_64 #1 SMP Mon Jun 27 19:49:27 BST 2011 x86_64 x86_64 x86_64 GNU/Linux
[root@centos60-fuj ~]# yum install grace
Loaded plugins: fastestmirror, refresh-packagekit
Determining fastest mirrors
* base: mirror.issp.co.th
* epel: mirror.neu.edu.cn
* extras: mirror.issp.co.th
* rpmforge: fr2.rpmfind.net
* updates: mirror.issp.co.th
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package grace.x86_64 0:5.1.22-7.el6 set to be updated
--> Processing Dependency: libnetcdf.so.6()(64bit) for package: grace-5.1.22-7.el6.x86_64
--> Finished Dependency Resolution
Error: Package: grace-5.1.22-7.el6.x86_64 (epel)
Requires: libnetcdf.so.6()(64bit)
Available: netcdf-4.1.1-3.el6.2.x86_64 (epel)
libnetcdf.so.6()(64bit)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

[/quote]

Did I break something by copying the .so ?

[pschaff]

I don't think so, as the package manager should not be aware of the copy operation. I suspect it is something to do with using multiple 3rd party repos without yum-plugin-priorities. On my x86_64 system:[code]
# rpm -q grace netcdf
grace-5.1.22-7.el6.x86_64
netcdf-4.1.1-3.el6.2.x86_64
# rpm -ql netcdf | grep libnetcdf
/usr/lib64/libnetcdf.so.6
/usr/lib64/libnetcdf.so.6.0.0
/usr/lib64/libnetcdf_c++.so.5
/usr/lib64/libnetcdf_c++.so.5.0.0
/usr/lib64/libnetcdff.so.5
/usr/lib64/libnetcdff.so.5.0.0[/code]

[centguy]

Okay, I install grace
by first uninstall netcdf.

Then I disable rpmforge and enable epel

and reinstall grace

It is working now.

From now on, I don't think I will use rpmforge.

The last time I checked rpmforge does not have gparted so I added epel.

And it seems epel is more complete and robust.

[pschaff]

All depends on your needs. EPEL is better for some things and RPMforge for others. What is certain is that mixing them (and other 3rd parry repos) is problematic and must be done with extreme care and attention to detail. If you are able to stick with a single 3rd party repo for needed packages life will be easier.

[centguy]

You are right.
I am experimenting a centos6.0 guest OS in VirtualBox so that I can reinforce my
understanding.
Once I disable rpmforge, I cannot install vlc. :(


So far epel gives me gparted, meld and grace.

rpmforge gives the all-important vlc, etc..

[pschaff]

yum-plugin-priorities is your friend, or use "enabled=0" in the repo configs and "--enablerepo" selectively. YMMV.