Red Hat Bugzilla – Bug 178974
[x86_64, s390x] gnome-games fails to rebuild
Last modified: 2007-11-30 17:07:22 EST
Description of problem:
rpmbuild --rebuild gnome-games fails
Version-Release number of selected component (if applicable):
rpmbuild --rebuild $SRPM
x86_64 rpmbuild --target=x86_64 --rebuild $SRPM
s390x rpmbuild --target=s390x --rebuild $SRPM
Steps to Reproduce:
gcc -O2 -g -pipe -m64 -o gnect main.o gfx.o prefs.o theme.o adjmtrx.o bintree.o
connect4.o evaluate.o heurist.o ia_main.o pbsolver.o playgame.o
-Wl,--export-dynamic -pthread -L/usr/X11R6/lib64 -lglade-2.0 -lgnomeui-2 -lSM
-lICE -lbonoboui-2 -lxml2 -lpthread -lz -lgnomecanvas-2 -lgnome-2
/usr/lib/libpopt.so -lart_lgpl_2 -lpangoft2-1.0 -lbonobo-2 -lgconf-2
-lgnomevfs-2 -lbonobo-activation -lORBit-2 -lgthread-2.0 -lgtk-x11-2.0
-lgdk-x11-2.0 -latk-1.0 -lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lrsvg-2
-lgdk_pixbuf-2.0 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0
/usr/lib/libpopt.so: could not read symbols: File in wrong format
collect2: ld returned 1 exit status
make: *** [gnect] Error 1
Note that /usr/lib64 is used in other places; there may be something
that could be fixed in a fairly straightforward manner.
The problem, I believe, is that the libtool that ships in the source tree was
generated with a buggy version of libtool.
So there are a few ways to attack this. These things sometimes work.
- We could try rerunning libtoolize or autoreconf at the very top of the %build
section of the spec file.
- We could try copying system libtool (/usr/bin/libtool) to the source tree
overwriting the buggy generated libtool.
- We could try passing a make variable that points to system libtool directly
(e.g., change a line that starts with make in the spec file to make
Any of these methods could fail for various reasons, though, and the problem
will be gone in RHEL5. This issue certianly isn't important enough to push an
update for or hold up an update for, but it might be reasonable to fix during an
update if we ever do another RHEL4 gnome-games update.
For now I'm going to close because we have plans to immediately fix the problem
and it will automatically be fixed in RHEL5.