Subject | Re: [firebird-php] PHP 5.2.5 with FB 2.1 |
---|---|
Author | Milan Babuskov |
Post date | 2008-01-25T17:16:30Z |
Jiri Cincura wrote:
so if you go static, you'll need to rebuild the entire PHP installation
(and make sure you build PHP as SAPI module, not CGI or CLI - and with
correct --prefix as well). If you change something (different values to
configure script), you might also need to rebuild Apache as well
(athough it is rare).
I feel much 'safer' to simply add interbase extension to the default PHP
install, then to rebuild PHP with zilion options in configure script. Of
course, you can always get the original configure line with phpinfo()
call, but still...
I also use PHP for command-line scripts, so it gives me Firebird support
for both SAPI and CLI variants of PHP (both installed on Slackware by
default, BTW), without having to compile PHP twice.
--
Milan Babuskov
http://www.flamerobin.org
> On 1/25/08, Milan Babuskov <milanb@...> wrote:By default, the Slackware install of Apache uses PHP as a SAPI module,
>> --with-interbase=shared,/opt/firebird
>
> Hmm, with shared it works. I'm building everything static. What's the
> difference (advantage) of having this dynamic in PHP
so if you go static, you'll need to rebuild the entire PHP installation
(and make sure you build PHP as SAPI module, not CGI or CLI - and with
correct --prefix as well). If you change something (different values to
configure script), you might also need to rebuild Apache as well
(athough it is rare).
I feel much 'safer' to simply add interbase extension to the default PHP
install, then to rebuild PHP with zilion options in configure script. Of
course, you can always get the original configure line with phpinfo()
call, but still...
I also use PHP for command-line scripts, so it gives me Firebird support
for both SAPI and CLI variants of PHP (both installed on Slackware by
default, BTW), without having to compile PHP twice.
--
Milan Babuskov
http://www.flamerobin.org