Bug 13141 - PHP3 spec file doesn't support MySQL well
Summary: PHP3 spec file doesn't support MySQL well
Keywords:
Status: CLOSED DUPLICATE of bug 10987
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: php
Version: 6.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-06-28 01:35 UTC by Bob Ramstad
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-06-28 01:35:14 UTC
Embargoed:


Attachments (Terms of Use)

Description Bob Ramstad 2000-06-28 01:35:13 UTC
howdy.  i tried to follow various directions to get PHP3 to build with 
MySQL support and had a lot of problems.

in particular, if i uncomment the various lines in the spec file to enable 
MySQL support, i get errors from the system that there is no "mysql" 
module.

i ended up hacking and slashing my way through it by manually taking the 
%post, %postun and %files mysql sections and slapping them on the main 
section.

the other thing i had to do (of course) was add a "--with-mysql" to the 
configuration line.

certainly for PHP4 it would be nice if this could get straightened out so 
it is easy to fix things up for MySQL support.  getting Apache + PHP + 
MySQL to work together seems to be a common task and it is more difficult 
than necessary as it stands now.

here's a really nutty idea... how about providing TWO spec files, with 
different names -- one php.spec and one php-mysql.spec?  that would avoid a 
whole lot of problems and might be the most elegant solution.

-- Bob

Comment 1 Nalin Dahyabhai 2000-06-28 01:44:01 UTC
This should already be resolved in Raw Hide (ftp://ftp.redhat.com/pub/rawhide/),
because PHP 4.0 now includes a bundled version of the MySQL client, and you need
only change a --without-mysql to a --with-mysql to enable it.

*** This bug has been marked as a duplicate of 10987 ***


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