Red Hat Bugzilla – Bug 73027
incorrect dependency on libgd breaks apache
Last modified: 2007-04-18 12:46:11 EDT
Description of Problem: There should be a dependency on libgd.so.1.8.4 (or the gd-1.8.4 package) - with gd-1.8.3 /usr/lib/apache/libphp4.so has an unresolved symbol (I ran into this trying to upgrade slowly and carefully from RH7.1 to RH7.3) Version-Release number of selected component (if applicable): php-4.1.2-7.3.4 and gd-1.8.3-7 How Reproducible: Install these packages Steps to Reproduce: Start Apache Actual Results: Apache fails to load libphp4.so, complaining about unresolved symbol gdStringFT Expected Results: Apache should have loaded Additional Information: I don't know if the procedure of upgrading Redhat versions bit by bit is officially "supported", but it is absolutely essential for upgrading a server while trying to keep services running as much as possible,
gdStringFT ? never heard of it. Doesn't even exist in the gd libs [root@dhcp59-221 root]# nm /usr/lib/libgd.* | grep -ic gdStringFT 0 [root@alpha php-4.1.2]# grep -irc gdStringFT * 0 Not directly referanced by anything in the php codebase either. google has never heard of it either... Sorry, I can find no referance to this gdStringFT in the codebase. Oh wait, you did a jump from 7.1 to 7.3? how as an upgrade install? As a rpm -Fvh against an RPMS directory?
Sorry, my mistake, that should be gdImageStringFT. It's in the 7.3 version of gd but not the 7.1 version. I upgraded by manually upgrading small dependency groups of RPMs at a time (actually using apt-rpm, but that just calls rpm -U to do its work).
Ok so it's a BuildRequires: gd >= 1.8 it's added for errata but for now as you've already seen, just update gd Phil =--=
surely it's "Requires: gd >= 1.8.4"? I wasn't trying to build it and the difference between 1.8.3 and 1.8.4 is significant, since it's in 1.8.4 that the symbol appears.
yes, sorry, not getting enuf sleep here...
Leaving this open whilst an errata is still pending.
*** Bug 78696 has been marked as a duplicate of this bug. ***
Thanks for the reports. This is fixed in all current releases.