PEAR 1.6
by Brandon Holbrook
All, what is our plan wrt php-pear-1.6? Are we going to update f7 or
just f8? Has that decision already been made or should that be an order
of business for the PHP SIG to discuss and decide? Honestly, I'm not
sure what the differences are between 1.5 and 1.6. Once we get a
decision I'll update the wiki.
Reason I'm asking: I was about to update Mail_Mime to the latest and
greatest but found that it requires pear-1.6, so it'll have to wait :)
-Brandon
16 years, 9 months
pecl rebuilds
by Brandon Holbrook
All,
After just upgrading one of my development boxes to f7, I started
getting a lot of PHP warnings when the PHP engine starts similar to the
following:
PHP Warning: PHP Startup: apc: Unable to initialize module
Module compiled with module API=20050922, debug=0, thread-safety=0
PHP compiled with module API=20060613, debug=0, thread-safety=0
and
PHP Warning: PHP Startup: mailparse: Unable to initialize module
Module compiled with module API=20050922, debug=0, thread-safety=0
PHP compiled with module API=20060613, debug=0, thread-safety=0
(apc has already been bugzilla'd at
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=244045)
apc and mailparse are the only 2 complaining on my box, and a quick "yum
list *pecl*" verifies both of these modules still bear a 'fc6' disttag.
Needless to say, since pecl modules are compiled against a specific PHP
version, this is unacceptable. In addition to rebuilding these packages
for f7 asap, I'd like to come up with a good policy about making
mandatory rebuilds of pecl packages whenever the PHP core ABI gets
updated. Is it reasonable to assume ABI updates only happen between
fedora releases, or do we need to also address planning simultaneous php
and php-pecl-* updates mid-release? Other thoughts?
-Brandon
16 years, 10 months
Changes to 'make install' in PHP 5.2.3
by Jeff Sheltren
Hi, just thought I'd give a heads up to prevent people from dealing
with the same problem I just went through...
I built PHP 5.2.3 by re-using the spec from the PHP SRPM in devel and
bumping the version. The problem is that as of 5.2.3, they've
changed the way 'make install' installs the cgi and cli binaries.
There is no longer a need to call 'make install-cli' separately as
now if you've configured for cgi, then both the cgi and cli versions
get installed with a 'make install'. Doing the install the old way
(as in the 5.2.2 RPM) leaves you with /usr/bin/php and /usr/bin/php-
cgi as the same binary which is the CLI and not the CGI.
To fix this, I changed the spec slightly, from:
# Install everything from the CGI SAPI build
pushd build-cgi
make install INSTALL_ROOT=$RPM_BUILD_ROOT
mv $RPM_BUILD_ROOT%{_bindir}/php $RPM_BUILD_ROOT%{_bindir}/php-cgi
# Install the CLI SAPI as /usr/bin/php
make install-cli INSTALL_ROOT=$RPM_BUILD_ROOT
popd
to:
# Install everything from the CGI SAPI build
pushd build-cgi
make install INSTALL_ROOT=$RPM_BUILD_ROOT
popd
That installs both /usr/bin/php (cli) and /usr/bin/php-cgi correctly.
-Jeff
16 years, 10 months
