Red Hat Bugzilla – Bug 153108
Error in configure prevents php SRPM rebuild on x86_64 w/ mssql module
Last modified: 2007-11-30 17:07:17 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.6) Gecko/20050322 Firefox/1.0.2 Red Hat/1.0.2-1.4.1
Description of problem:
Attempting to rebuild the php SRPM in order to add the php-mssql rpm will not work on x86_64. The required FreeTDS library has been downloaded and built as an rpm. However the ./configure script looks only in /usr/lib for the neccessary libtds.a while libtds.a is in /usr/lib64/ on x86_64 builds.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
On x86_64 system:
1. Download the latest FreeTDS stable source:
2. Build freetds RPMS:
mv freetds-stable.tgz freetds-0.62.4.tar.gz; rpmbuild -ta freetds-0.62.4.tar.gz
3. Install freetds and freetds-devel
rpm -Uvh freetds-0.62.4-1.x86_64.rpm freetds-devel-0.62.4-1.x86_64.rpm
4. Acquire php SRPM:
up2date --get-source php
5. Attempt to rebuild php with mssql support included:
rpmbuild --rebuild --define '_with_mssql 1' \
<snipped ./configure output>
checking for MSSQL support via FreeTDS... yes, shared
configure: error: Could not find /usr/lib/libtds.a
Actual Results: rpmbuild fails, no php-mssql.x86_64 generated.
Expected Results: rpmbuild succeeds and generates the needed php-mssql rpm
modifying php-4.3.9/ext/mssql/config.m4 to look for libtds.a in both lib and lib64 fixes the issue (patch not included because my I'm sure I didn't fix it the "right way", just works for me).
Please don't be afraid to attach patches, however ugly ;) But essentially yes
the hacky way is used in PHP 4.3.x. I've fixed it more cleanly upstream.
An experimental test source RPM is available here:
which should fix this issue; please report any feedback from testing.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.