I was trying to build frysk with "-m64" on ppc64. After adding "-m64" to the
compilers in EXPORT, I got some errors that skip incompatible libraries in
/usr/lib/, /usr/lib/gcc/ppc-redhat-linux/3.4.3/../../../ and so on.
After making the following symbol links under /usr/lib64, no such errors any more:
./libatk-1.0.so -> libatk-1.0.so.0.800.0
./libexpat.so -> libexpat.so.0.5.0
./libfontconfig.so -> libfontconfig.so.1.0.4
./libfreetype.so -> libfreetype.so.6.3.7
./libglib-2.0.so -> libglib-2.0.so.0.400.7
./libgmodule-2.0.so -> libgmodule-2.0.so.0.400.7
./libgobject-2.0.so -> libgobject-2.0.so.0.400.7
./libjpeg.so -> libjpeg.so.62.0.0
./libpng12.so -> libpng12.so.0.1.2.7
./libtiff.so -> libtiff.so.3.6
./libvte.so -> libvte.so.4.4.0
./libxml2.so -> libxml2.so.2.6.16
Not sure if this is the right fix, but the build can get continued after those
BTW. I build frysk on a freshly-installed RHEL4 U3 Beta1 (got from rhn.redhat.com)
That looks like mis-installed or bad system RPM, the links should definitly be
there. On an x86-64 machine I see:
ls -l /usr/lib64/libvte*.so
lrwxrwxrwx 1 root root 15 Jan 20 15:47 /usr/lib64/libvte.so -> libvte.so.4.4.0
It seems that RHEL only provide 32-bits development libraries on PPC64. Can I
request the 64-bits libraries also provided?
Besides these symbol links, their responsive pkgconfig description files are
also needed in /usr/lib64/pkgconfig/
All the 64-bit libraries, except libvte.so(which is not needed by frysk), could
be found on RHEL5 alpha1. Here are some RPMs about these libraries in RHEL5
Close this bug
These 64-bit libraries are also on FC6 test1.
But I am not sure if these 64-bit libraries will be in the latest FC5 update. My
idea is to let this open until we can verify that FC5 update includes these
So I re-open this bug.
We also found some other 64-bit libraries missing for building frysk on ppc64.
Will open another bug to track this. Thanks.
Fixed for FC6. Close.