Bug 97311 - PHP Src RPM fails with GD errors
PHP Src RPM fails with GD errors
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: php (Show other bugs)
9
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Joe Orton
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-06-12 16:45 EDT by Stephen Lawrence Jr.
Modified: 2007-04-18 12:54 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-06-12 16:58:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Stephen Lawrence Jr. 2003-06-12 16:45:57 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
php-4.2.2-19.src.rpm

When trying to rebuild php from the src rpm:

rpmbuild -ba php.spec

....snip

Making all in gd
make[2]: Entering directory `/usr/src/redhat/BUILD/php-4.2.2/build-cgi/ext/gd'
make[3]: Entering directory `/usr/src/redhat/BUILD/php-4.2.2/build-cgi/ext/gd'
gcc -I. -I/usr/src/redhat/BUILD/php-4.2.2/ext/gd
-I/usr/src/redhat/BUILD/php-4.2.2/build-cgi/main
-I/usr/src/redhat/BUILD/php-4.2.2
-I/usr/src/redhat/BUILD/php-4.2.2/build-cgi/Zend -I/usr/include/libxml2
-I/usr/include/freetype2/freetype -I/usr/include/imap -I/usr/include/mysql
-I/u01/app/oracle/product/8.1.7/rdbms/public
-I/u01/app/oracle/product/8.1.7/rdbms/demo
-I/u01/app/oracle/product/8.1.7/network/public -I/usr/local/include
-I/usr/include/pspell -I/usr/include/ucd-snmp
-I/usr/src/redhat/BUILD/php-4.2.2/main -I/usr/src/redhat/BUILD/php-4.2.2/Zend
-I/usr/src/redhat/BUILD/php-4.2.2/TSRM  -DUCD_COMPATIBLE
-I/usr/src/redhat/BUILD/php-4.2.2/build-cgi/TSRM -O2 -g -march=i386 -mcpu=i686
-fPIC  -c /usr/src/redhat/BUILD/php-4.2.2/ext/gd/gd.c && touch gd.lo
In file included from /usr/src/redhat/BUILD/php-4.2.2/ext/gd/gd.c:83:
/usr/src/redhat/BUILD/php-4.2.2/ext/gd/gd_ctx.c: In function
`_php_image_output_ctx':
/usr/src/redhat/BUILD/php-4.2.2/ext/gd/gd_ctx.c:70: structure has no member
named `gd_free'
/usr/src/redhat/BUILD/php-4.2.2/ext/gd/gd_ctx.c:98: structure has no member
named `gd_free'
/usr/src/redhat/BUILD/php-4.2.2/ext/gd/gd.c: In function `_php_image_type':
/usr/src/redhat/BUILD/php-4.2.2/ext/gd/gd.c:1014: structure has no member named
`gd_free'
/usr/src/redhat/BUILD/php-4.2.2/ext/gd/gd.c:1017: structure has no member named
`gd_free'
/usr/src/redhat/BUILD/php-4.2.2/ext/gd/gd.c: In function `_php_image_create_from':
/usr/src/redhat/BUILD/php-4.2.2/ext/gd/gd.c:1208: structure has no member named
`gd_free'
make[3]: *** [gd.lo] Error 1
make[3]: Leaving directory `/usr/src/redhat/BUILD/php-4.2.2/build-cgi/ext/gd'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/src/redhat/BUILD/php-4.2.2/build-cgi/ext/gd'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/redhat/BUILD/php-4.2.2/build-cgi/ext'
make: *** [all-recursive] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.17336 (%build)


RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.17336 (%build)


Version-Release number of selected component (if applicable):
php-4.2.2-19.src.rpm

How reproducible:
Always

Steps to Reproduce:
1. download src rpm
2. rpmbuild -ba php.spec
3.
    

Actual Results:  Error in gd section

Expected Results:  rpm should have told me if there were a missing package.

Additional info:
Comment 1 Stephen Lawrence Jr. 2003-06-12 16:58:52 EDT
The src rpm was rawhide. I don't know if it should have checked the version #'s
of my other non-rawhide packages or not, but when I tried to rpm -ba with the
rh9.0 src php rpm it did not fail at that point.
Comment 2 Joe Orton 2003-06-12 17:09:23 EDT
Yes, this will happen if you build old php package against a new gd package. 
Use old gd and old php or new gd and php and you should be OK, if that makes sense.

Note You need to log in before you can comment on or make changes to this bug.