From NWChem
Viewed 2720 times, With a total of 2 Posts
|
|
|
Just Got Here
Threads 1
Posts 1
|
|
| 2:41:36 PM PDT - Mon, Apr 23rd 2012 |
|
Hello,
I am trying to execute either full ecce or just the builder but get, in either case:
./builder: symbol lookup error: /usr/lib64/gtk-2.0/modules/libpk-gtk-module.so: undefined symbol: FcLangGetCharSet
I am running RHE Server Release 6.2 and GNOME 2.28.2. Kernel 2.6.32-220.2.1.el6.x86_64
Running ldd on builder gives:
ldd /opt/ECCE/BUILDER/ecce-builder-v6.3/rhel5-gcc4.1.2-m64/bin/builder
linux-vdso.so.1 => (0x00007fffecbff000)
libeccewxguicomm.so => not found
libeccewxviz.so => not found
libeccewxinv.so => not found
libeccevizsg.so => not found
libeccemoiv.so => not found
libecceinv.so => not found
libeccecommxt.so => not found
libeccecomm.so => not found
libeccercmd.so => not found
libeccewxgui.so => not found
libeccewxplotctrl.so => not found
libeccewxthings.so => not found
libecceedsi.so => not found
libeccedav.so => not found
libeccecipc.so => not found
libeccefaces.so => not found
libeccexml.so => not found
libeccetdat.so => not found
libecceutil.so => not found
libutil.so.1 => /lib64/libutil.so.1 (0x0000003554800000)
libxerces-c.so.28 => not found
libxerces-depdom.so.28 => not found
libwx_gtk2_ewxaui-2.8.so => not found
libwx_gtk2_adv-2.8.so.0 => not found
libwx_gtk2_richtext-2.8.so.0 => not found
libwx_gtk2_aui-2.8.so.0 => not found
libwx_gtk2_xrc-2.8.so.0 => not found
libwx_gtk2_qa-2.8.so.0 => not found
libwx_gtk2_html-2.8.so.0 => not found
libwx_gtk2_core-2.8.so.0 => not found
libwx_base_xml-2.8.so.0 => not found
libwx_base_net-2.8.so.0 => not found
libwx_base-2.8.so.0 => not found
libXt.so.6 => /usr/lib64/libXt.so.6 (0x00007f9a85297000)
libX11.so.6 => /usr/lib64/libX11.so.6 (0x0000003549800000)
libwx_gtk2_gl-2.8.so.0 => not found
libGL.so.1 => /usr/lib64/libGL.so.1 (0x0000003550c00000)
libGLU.so.1 => /usr/lib64/libGLU.so.1 (0x0000003546c00000)
libjpeg.so.62 => /usr/lib64/libjpeg.so.62 (0x0000003554c00000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x0000003552000000)
libm.so.6 => /lib64/libm.so.6 (0x0000003546400000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0000003550400000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f9a85078000)
libc.so.6 => /lib64/libc.so.6 (0x0000003546000000)
libSM.so.6 => /usr/lib64/libSM.so.6 (0x0000003553800000)
libICE.so.6 => /usr/lib64/libICE.so.6 (0x0000003553400000)
libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x0000003549400000)
libdl.so.2 => /lib64/libdl.so.2 (0x0000003546800000)
libnvidia-tls.so.290.10 => /usr/lib64/tls/libnvidia-tls.so.290.10 (0x0000003550000000)
libnvidia-glcore.so.290.10 => /usr/lib64/libnvidia-glcore.so.290.10 (0x00007f9a82d6e000)
libXext.so.6 => /usr/lib64/libXext.so.6 (0x000000354a400000)
/lib64/ld-linux-x86-64.so.2 (0x0000003545c00000)
libuuid.so.1 => /lib64/libuuid.so.1 (0x0000003551800000)
libXau.so.6 => /usr/lib64/libXau.so.6 (0x0000003549000000)
Thank you,
-Martin.
|
|
|
|
|
|
Gets Around
Threads 2
Posts 82
|
|
| 4:58:29 PM PDT - Mon, Apr 23rd 2012 |
|
Martin,
Let's try to solve the builder issue and then move on to full ECCE. In order for an ldd command to work you would need to source the ecce_env script (I'm assuming you've already sourced the runtime_setup script). Another probably easier way to do it is to put the ldd command in the ebuilder script that is used to start the builder (it's just a a C shell script that sets up the environment and then starts the builder executable). Edit $ECCE_HOME/scripts/ebuilder and right before the very last line that starts builder add the following line:
ldd ./builder
Then save the change and run ebuilder again and you should get an accurate accounting of what shared libraries are being used. Post that in a reply to this thread and we'll proceed from there.
This looks to be different though than a missing shared library, but I think that's a good place to start. I've not seen this libpk-gtk-module.so before and we don't explicitly link with it. I'm guessing some other GTK library references it.
We can try to work through this issue, and should at least give it a try and see how difficult it proves. But, I'm also going to recommend that you download the ECCE source code distribution and build that. It's much more likely to work for you without issues since it will be compiled directly on your platform using your local libraries like GTK that is related to the problem you are having. Platform-specific problems is a major reason why there is now an ECCE source code distribution. It's really quite simple to build ECCE using the documentation in the $ECCE_HOME/build/README file after you extract the distribution (check the release notes if this isn't clear). There is an automated script that will build all the code for you including some third party packages. Depending on your platform it's typically a couple hours to build ECCE with the third party packages it needs. Only a few minutes of that time is you entering commands and the rest is just the ECCE build script and the compilation itself plugging away.
Finally, I did a google search on the error message you are getting. It indicated that by using KDE instead of Gnome the problem should go away. But, I understand you probably don't want to be switching window managers as a work around.
Gary
|
|
Edited On 5:01:23 PM PDT - Mon, Apr 23rd 2012 by Gary
|
|
|
|
|
|
Gets Around
Threads 2
Posts 82
|
|
| 5:14:05 PM PDT - Mon, Apr 23rd 2012 |
|
Martin,
If you're adventurous, you could take a look at this discussion of what looks like a related "packagekit-gnome" problem: https://bugs.launchpad.net/ubuntu/+source/packagekit-gnome/+bug/389766
It indicates that you can tell Gnome not load this library by editing a configuration file so maybe that's a better work around than using KDE at least.
Gary
|
|
Edited On 5:15:06 PM PDT - Mon, Apr 23rd 2012 by Gary
|
|
|
AWC's:
2.5.10 MediaWiki - Stand Alone Forum Extension
Forum theme style by: AWC
