How can I install the php-interbase extension with PHP? I have found no options for that in YAST and if I compile it from source from php.org with the option, it is not recognized by Apache. SuSE intalls it in /usr/share/php and the source installs it in /usr/local/lib/php. Art
On Tue, 18 Feb 2003, Art Fore wrote:
How can I install the php-interbase extension with PHP? I have found no options for that in YAST and if I compile it from source from php.org with the option, it is not recognized by Apache. SuSE intalls it in /usr/share/php and the source installs it in /usr/local/lib/php.
Hello Many applications, when compiled from source, installs by default under /usr/local/appname, but practically all distributors, such as Suse, does not like this approach that much. Distributions often install, say, Apache, into several folders: executable goes under /usr/sbin, libraries under /usr/lib, configuration files under /etc and so on. Now, if you compile and install www.php.net version of PHP yourself, and if you want to have it installed with Apache installed by Suse's Yast, you have to specify these folders where configuration and Apache modules go. I have done this with Suse 7.3 once, to test the procedure out, but otherwise I have always compiled both Apache and PHP from source by myself, as I have found it easier to manage. Another thing is, that you better remove the mod_php.rpm installed by Suse Yast before compiling & installing this new PHP, as next time Suse makes update for mod_php available, it naturally installs it over your copy. Compiling Apache and PHP to support Interbase is fairly trivial. Apache (1.3.x): ./configure --enable-module=so make; make install PHP4.x: ./configure --with-apxs=/usr/local/apache/bin/apxs \ --with-interbase/path/to/interbase --with-mysql (and so on with other opts) make; make install Then you have to modify the httpd.conf under /usr/local/apache/conf to load the mod_php by LoadModule and associate .php with that module. This is explained in PHP's INSTALL file. If you need more help, mail to this or suse-linux-e list. Cheers, -- --Jyry :-( C:-/ C========8-O C8-/ C:-(
Can anyone tell me where I can get the php4-4.2.2 srm for SuSE? Art Jyry Kuukkanen wrote:
On Tue, 18 Feb 2003, Art Fore wrote:
How can I install the php-interbase extension with PHP? I have found no options for that in YAST and if I compile it from source from php.org with the option, it is not recognized by Apache. SuSE intalls it in /usr/share/php and the source installs it in /usr/local/lib/php.
Hello
Many applications, when compiled from source, installs by default under /usr/local/appname, but practically all distributors, such as Suse, does not like this approach that much. Distributions often install, say, Apache, into several folders: executable goes under /usr/sbin, libraries under /usr/lib, configuration files under /etc and so on.
Now, if you compile and install www.php.net version of PHP yourself, and if you want to have it installed with Apache installed by Suse's Yast, you have to specify these folders where configuration and Apache modules go.
I have done this with Suse 7.3 once, to test the procedure out, but otherwise I have always compiled both Apache and PHP from source by myself, as I have found it easier to manage.
Another thing is, that you better remove the mod_php.rpm installed by Suse Yast before compiling & installing this new PHP, as next time Suse makes update for mod_php available, it naturally installs it over your copy.
Compiling Apache and PHP to support Interbase is fairly trivial.
Apache (1.3.x): ./configure --enable-module=so make; make install
PHP4.x: ./configure --with-apxs=/usr/local/apache/bin/apxs \ --with-interbase/path/to/interbase --with-mysql (and so on with other opts) make; make install
Then you have to modify the httpd.conf under /usr/local/apache/conf to load the mod_php by LoadModule and associate .php with that module. This is explained in PHP's INSTALL file.
If you need more help, mail to this or suse-linux-e list.
Cheers,
Apache is OK with PHP as I can connect to a postgresql database with it via webadmin and via phrojekt. Have not found anyway to get the interbase.so or to comile it from source. When I compiled it from source, then Apache could not find it as could nothing else. (I uninstalled the SuSE PHP before this). I installed the SuSE PHP4 again along with the php-devel, and tried to create the interbase.so file per an email from the ibsupport mail list, still does not work I guess because SuSE has bastardized it so much. Tried many suggestions, none work for one reason or another including the apxs which does not exist. If I install the source files from php.net and compile, how do I get anything else to find the damned thing (php that is)? Art Jyry Kuukkanen wrote:
On Tue, 18 Feb 2003, Art Fore wrote:
How can I install the php-interbase extension with PHP? I have found no options for that in YAST and if I compile it from source from php.org with the option, it is not recognized by Apache. SuSE intalls it in /usr/share/php and the source installs it in /usr/local/lib/php.
Hello
Many applications, when compiled from source, installs by default under /usr/local/appname, but practically all distributors, such as Suse, does not like this approach that much. Distributions often install, say, Apache, into several folders: executable goes under /usr/sbin, libraries under /usr/lib, configuration files under /etc and so on.
Now, if you compile and install www.php.net version of PHP yourself, and if you want to have it installed with Apache installed by Suse's Yast, you have to specify these folders where configuration and Apache modules go.
I have done this with Suse 7.3 once, to test the procedure out, but otherwise I have always compiled both Apache and PHP from source by myself, as I have found it easier to manage.
Another thing is, that you better remove the mod_php.rpm installed by Suse Yast before compiling & installing this new PHP, as next time Suse makes update for mod_php available, it naturally installs it over your copy.
Compiling Apache and PHP to support Interbase is fairly trivial.
Apache (1.3.x): ./configure --enable-module=so make; make install
PHP4.x: ./configure --with-apxs=/usr/local/apache/bin/apxs \ --with-interbase/path/to/interbase --with-mysql (and so on with other opts) make; make install
Then you have to modify the httpd.conf under /usr/local/apache/conf to load the mod_php by LoadModule and associate .php with that module. This is explained in PHP's INSTALL file.
If you need more help, mail to this or suse-linux-e list.
Cheers,
On Thu, 20 Feb 2003, Art Fore wrote:
Apache is OK with PHP as I can connect to a postgresql database with it via webadmin and via phrojekt. Have not found anyway to get the interbase.so or to comile it from source. When I compiled it from source, then Apache could not find it as could nothing else. (I uninstalled the SuSE PHP before this).
I installed the SuSE PHP4 again along with the php-devel, and tried to create the interbase.so file per an email from the ibsupport mail list, still does not work I guess because SuSE has bastardized it so much. Tried many suggestions, none work for one reason or another including the apxs which does not exist.
If I install the source files from php.net and compile, how do I get anything else to find the damned thing (php that is)?
Art
Hello again :-) While you have the Suse PHP and Apache installed, write and test a little PHP script, say, test.php: <? echo phpinfo(); ?> Now, place it somewhere in your test site and have a look at it with your browser. It will print you a page with all sorts of information on PHP. Take a look at "Configure Command" - that includes the ./configure line that the Suse mod_php was compiled with. So, download the latest and greatest of PHP, unpack it, use the configuration command printed by phpinfo and add your Interbase option to the end, make & make install. Then you need to restart your Apache. Have another look at your marvellous test.php and it should print information of your newly build mod_php. It might be a good idea to save the phpinfo configuration command to a file, say, "phpconf": #!/bin/sh ./configure --prefix=/some/suse/place etc.... This way it is safer than using phpinfo page, as your Apache might be down and cannot be started. I hope this helps. Cheers, --jq
Jyry Kuukkanen wrote:
On Tue, 18 Feb 2003, Art Fore wrote:
How can I install the php-interbase extension with PHP? I have found no options for that in YAST and if I compile it from source from php.org with the option, it is not recognized by Apache. SuSE intalls it in /usr/share/php and the source installs it in /usr/local/lib/php.
Hello
Many applications, when compiled from source, installs by default under /usr/local/appname, but practically all distributors, such as Suse, does not like this approach that much. Distributions often install, say, Apache, into several folders: executable goes under /usr/sbin, libraries under /usr/lib, configuration files under /etc and so on.
Now, if you compile and install www.php.net version of PHP yourself, and if you want to have it installed with Apache installed by Suse's Yast, you have to specify these folders where configuration and Apache modules go.
I have done this with Suse 7.3 once, to test the procedure out, but otherwise I have always compiled both Apache and PHP from source by myself, as I have found it easier to manage.
Another thing is, that you better remove the mod_php.rpm installed by Suse Yast before compiling & installing this new PHP, as next time Suse makes update for mod_php available, it naturally installs it over your copy.
Compiling Apache and PHP to support Interbase is fairly trivial.
Apache (1.3.x): ./configure --enable-module=so make; make install
PHP4.x: ./configure --with-apxs=/usr/local/apache/bin/apxs \ --with-interbase/path/to/interbase --with-mysql (and so on with other opts) make; make install
Then you have to modify the httpd.conf under /usr/local/apache/conf to load the mod_php by LoadModule and associate .php with that module. This is explained in PHP's INSTALL file.
If you need more help, mail to this or suse-linux-e list.
Cheers,
-- --Jyry :-( C:-/ C========8-O C8-/ C:-(
Still no luck. Complains about apxs not being installed, so I remove that, then it complains about curl, so I remove that, then it complains about t1lib. This makes no sense at all. How does the SuSE PHP get installed if this the configuration for it? Here is the results of the phpinfo script. ./configure --prefix=/usr/share --datadir=/usr/share/php --bindir=/usr/bin --libdir=/usr/share --enable-shmop --enable-sigchild --enable-sysvsem --enable-sysvshm --enable-track-vars --enable-trans-sid --enable-versioning --enable-wddx --includedir=/usr/include --with-_lib=lib --with-config-file-path=/etc --with-exec-dir=/usr/lib/php/bin --disable-debug --enable-bcmath --enable-calendar --enable-ctype --enable-dbase --enable-discard-path --enable-exif --enable-filepro --enable-force-cgi-redirect --enable-ftp --enable-gd-imgstrttf --enable-gd-native-ttf --enable-inline-optimization --enable-magic-quotes --enable-mbstr-enc-trans --enable-mbstring --enable-memory-limit --enable-safe-mode --enable-shmop --enable-sigchild --enable-sysvsem --enable-sysvshm --enable-track-vars --enable-trans-sid --enable-versioning --enable-wddx --enable-yp --with-bz2 --with-dom=/usr/include/libxml2 --with-ftp --with-gdbm --with-gettext --with-gmp --with-imap=yes --with-iodbc --with-jpeg-dir=/usr --with-ldap=yes --with-mcal=/usr --with-mcrypt --with-mysql=/usr --with-ndbm --with-pgsql=/usr --with-png-dir=/usr--with-qtdom=/usr/lib/qt2 --with-snmp --with-t1lib --with-tiff-dir=/usr --with-ttf --with-freetype-dir=yes --with-xml --with-xpm-dir=/usr/X11R6 --with-zlib=yes --with-gd=shared --with-openssl --with-curl --with-swf=./dist/ --with-imap-ssl --enable-xslt --with-xslt-sablot --with-mm --with-apxs=/usr/sbin/apxs --with-interbase=/opt/interbase i586-suse-linux Does the same thing with or without i586-suse-linux, so what is it for? Art Jyry Kuukkanen wrote:
On Thu, 20 Feb 2003, Art Fore wrote:
Apache is OK with PHP as I can connect to a postgresql database with it via webadmin and via phrojekt. Have not found anyway to get the interbase.so or to comile it from source. When I compiled it from source, then Apache could not find it as could nothing else. (I uninstalled the SuSE PHP before this).
I installed the SuSE PHP4 again along with the php-devel, and tried to create the interbase.so file per an email from the ibsupport mail list, still does not work I guess because SuSE has bastardized it so much. Tried many suggestions, none work for one reason or another including the apxs which does not exist.
If I install the source files from php.net and compile, how do I get anything else to find the damned thing (php that is)?
Art
Hello again :-)
While you have the Suse PHP and Apache installed, write and test a little PHP script, say, test.php: <? echo phpinfo(); ?>
Now, place it somewhere in your test site and have a look at it with your browser. It will print you a page with all sorts of information on PHP. Take a look at "Configure Command" - that includes the ./configure line that the Suse mod_php was compiled with.
So, download the latest and greatest of PHP, unpack it, use the configuration command printed by phpinfo and add your Interbase option to the end, make & make install.
Then you need to restart your Apache. Have another look at your marvellous test.php and it should print information of your newly build mod_php.
It might be a good idea to save the phpinfo configuration command to a file, say, "phpconf":
#!/bin/sh ./configure --prefix=/some/suse/place etc....
This way it is safer than using phpinfo page, as your Apache might be down and cannot be started.
I hope this helps.
Cheers, --jq
Jyry Kuukkanen wrote:
On Tue, 18 Feb 2003, Art Fore wrote:
How can I install the php-interbase extension with PHP? I have found no options for that in YAST and if I compile it from source from php.org with the option, it is not recognized by Apache. SuSE intalls it in /usr/share/php and the source installs it in /usr/local/lib/php.
Hello
Many applications, when compiled from source, installs by default under /usr/local/appname, but practically all distributors, such as Suse, does not like this approach that much. Distributions often install, say, Apache, into several folders: executable goes under /usr/sbin, libraries under /usr/lib, configuration files under /etc and so on.
Now, if you compile and install www.php.net version of PHP yourself, and if you want to have it installed with Apache installed by Suse's Yast, you have to specify these folders where configuration and Apache modules go.
I have done this with Suse 7.3 once, to test the procedure out, but otherwise I have always compiled both Apache and PHP from source by myself, as I have found it easier to manage.
Another thing is, that you better remove the mod_php.rpm installed by Suse Yast before compiling & installing this new PHP, as next time Suse makes update for mod_php available, it naturally installs it over your copy.
Compiling Apache and PHP to support Interbase is fairly trivial.
Apache (1.3.x): ./configure --enable-module=so make; make install
PHP4.x: ./configure --with-apxs=/usr/local/apache/bin/apxs \ --with-interbase/path/to/interbase --with-mysql (and so on with other opts) make; make install
Then you have to modify the httpd.conf under /usr/local/apache/conf to load the mod_php by LoadModule and associate .php with that module. This is explained in PHP's INSTALL file.
If you need more help, mail to this or suse-linux-e list.
Cheers,
I added a bunch of the developement packages with yast and got through to whatg appears to be 1 last problem. Get the following last couple of lines from the ./configure checking return type of qsort... (cached) void Configure: error: Cannot find header files under /usr Can you tell me what this means and how to solve it? Art Art Fore wrote:
Still no luck. Complains about apxs not being installed, so I remove that, then it complains about curl, so I remove that, then it complains about t1lib. This makes no sense at all. How does the SuSE PHP get installed if this the configuration for it?
Here is the results of the phpinfo script.
./configure --prefix=/usr/share --datadir=/usr/share/php --bindir=/usr/bin --libdir=/usr/share --enable-shmop --enable-sigchild --enable-sysvsem --enable-sysvshm --enable-track-vars --enable-trans-sid --enable-versioning --enable-wddx --includedir=/usr/include --with-_lib=lib --with-config-file-path=/etc --with-exec-dir=/usr/lib/php/bin --disable-debug --enable-bcmath --enable-calendar --enable-ctype --enable-dbase --enable-discard-path --enable-exif --enable-filepro --enable-force-cgi-redirect --enable-ftp --enable-gd-imgstrttf --enable-gd-native-ttf --enable-inline-optimization --enable-magic-quotes --enable-mbstr-enc-trans --enable-mbstring --enable-memory-limit --enable-safe-mode --enable-shmop --enable-sigchild --enable-sysvsem --enable-sysvshm --enable-track-vars --enable-trans-sid --enable-versioning --enable-wddx --enable-yp --with-bz2 --with-dom=/usr/include/libxml2 --with-ftp --with-gdbm --with-gettext --with-gmp --with-imap=yes --with-iodbc --with-jpeg-dir=/usr --with-ldap=yes --with-mcal=/usr --with-mcrypt --with-mysql=/usr --with-ndbm --with-pgsql=/usr --with-png-dir=/usr--with-qtdom=/usr/lib/qt2 --with-snmp --with-t1lib --with-tiff-dir=/usr --with-ttf --with-freetype-dir=yes --with-xml --with-xpm-dir=/usr/X11R6 --with-zlib=yes --with-gd=shared --with-openssl --with-curl --with-swf=./dist/ --with-imap-ssl --enable-xslt --with-xslt-sablot --with-mm --with-apxs=/usr/sbin/apxs --with-interbase=/opt/interbase i586-suse-linux
Does the same thing with or without i586-suse-linux, so what is it for?
Art
Jyry Kuukkanen wrote:
On Thu, 20 Feb 2003, Art Fore wrote:
Apache is OK with PHP as I can connect to a postgresql database with it via webadmin and via phrojekt. Have not found anyway to get the interbase.so or to comile it from source. When I compiled it from source, then Apache could not find it as could nothing else. (I uninstalled the SuSE PHP before this).
I installed the SuSE PHP4 again along with the php-devel, and tried to create the interbase.so file per an email from the ibsupport mail list, still does not work I guess because SuSE has bastardized it so much. Tried many suggestions, none work for one reason or another including the apxs which does not exist.
If I install the source files from php.net and compile, how do I get anything else to find the damned thing (php that is)?
Art
Hello again :-)
While you have the Suse PHP and Apache installed, write and test a little PHP script, say, test.php: <? echo phpinfo(); ?>
Now, place it somewhere in your test site and have a look at it with your browser. It will print you a page with all sorts of information on PHP. Take a look at "Configure Command" - that includes the ./configure line that the Suse mod_php was compiled with.
So, download the latest and greatest of PHP, unpack it, use the configuration command printed by phpinfo and add your Interbase option to the end, make & make install.
Then you need to restart your Apache. Have another look at your marvellous test.php and it should print information of your newly build mod_php.
It might be a good idea to save the phpinfo configuration command to a file, say, "phpconf":
#!/bin/sh ./configure --prefix=/some/suse/place etc....
This way it is safer than using phpinfo page, as your Apache might be down and cannot be started.
I hope this helps.
Cheers, --jq
Jyry Kuukkanen wrote:
On Tue, 18 Feb 2003, Art Fore wrote:
How can I install the php-interbase extension with PHP? I have found no options for that in YAST and if I compile it from source from php.org with the option, it is not recognized by Apache. SuSE intalls it in /usr/share/php and the source installs it in /usr/local/lib/php.
Hello
Many applications, when compiled from source, installs by default under /usr/local/appname, but practically all distributors, such as Suse, does not like this approach that much. Distributions often install, say, Apache, into several folders: executable goes under /usr/sbin, libraries under /usr/lib, configuration files under /etc and so on.
Now, if you compile and install www.php.net version of PHP yourself, and if you want to have it installed with Apache installed by Suse's Yast, you have to specify these folders where configuration and Apache modules go.
I have done this with Suse 7.3 once, to test the procedure out, but otherwise I have always compiled both Apache and PHP from source by myself, as I have found it easier to manage.
Another thing is, that you better remove the mod_php.rpm installed by Suse Yast before compiling & installing this new PHP, as next time Suse makes update for mod_php available, it naturally installs it over your copy.
Compiling Apache and PHP to support Interbase is fairly trivial.
Apache (1.3.x): ./configure --enable-module=so make; make install
PHP4.x: ./configure --with-apxs=/usr/local/apache/bin/apxs \ --with-interbase/path/to/interbase --with-mysql (and so on with other opts) make; make install
Then you have to modify the httpd.conf under /usr/local/apache/conf to load the mod_php by LoadModule and associate .php with that module. This is explained in PHP's INSTALL file.
If you need more help, mail to this or suse-linux-e list.
Cheers,
On Fri, 21 Feb 2003, Art Fore wrote:
I added a bunch of the developement packages with yast and got through to whatg appears to be 1 last problem. Get the following last couple of lines from the ./configure
checking return type of qsort... (cached) void Configure: error: Cannot find header files under /usr
Can you tell me what this means and how to solve it?
Art
Hello I have not encountered that kind of a problem. Maybe you should try: make clean and then ./configure once again. If that does not help, then it might be a good idea to strip down the configure options to the minimum: ./configure --prefix=/usr/share --datadir=/usr/share/php --with-apxs --bindir=/usr/bin --libdir=/usr/share --with-apxs=/usr/sbin/apxs --with-interbase=/opt/interbase i586-suse-linux Can you configure, make and make install that without a problem? If so, then you may start adding extra options to your configure to sort out what is causing the trouble. Personally, I would not configure all that the Suse mod_php has been compiled with :-) Cheers, --jq
Art Fore wrote:
Still no luck. Complains about apxs not being installed, so I remove that, then it complains about curl, so I remove that, then it complains about t1lib. This makes no sense at all. How does the SuSE PHP get installed if this the configuration for it?
Here is the results of the phpinfo script.
./configure --prefix=/usr/share --datadir=/usr/share/php --bindir=/usr/bin --libdir=/usr/share --enable-shmop --enable-sigchild --enable-sysvsem --enable-sysvshm --enable-track-vars --enable-trans-sid --enable-versioning --enable-wddx --includedir=/usr/include --with-_lib=lib --with-config-file-path=/etc --with-exec-dir=/usr/lib/php/bin --disable-debug --enable-bcmath --enable-calendar --enable-ctype --enable-dbase --enable-discard-path --enable-exif --enable-filepro --enable-force-cgi-redirect --enable-ftp --enable-gd-imgstrttf --enable-gd-native-ttf --enable-inline-optimization --enable-magic-quotes --enable-mbstr-enc-trans --enable-mbstring --enable-memory-limit --enable-safe-mode --enable-shmop --enable-sigchild --enable-sysvsem --enable-sysvshm --enable-track-vars --enable-trans-sid --enable-versioning --enable-wddx --enable-yp --with-bz2 --with-dom=/usr/include/libxml2 --with-ftp --with-gdbm --with-gettext --with-gmp --with-imap=yes --with-iodbc --with-jpeg-dir=/usr --with-ldap=yes --with-mcal=/usr --with-mcrypt --with-mysql=/usr --with-ndbm --with-pgsql=/usr --with-png-dir=/usr--with-qtdom=/usr/lib/qt2 --with-snmp --with-t1lib --with-tiff-dir=/usr --with-ttf --with-freetype-dir=yes --with-xml --with-xpm-dir=/usr/X11R6 --with-zlib=yes --with-gd=shared --with-openssl --with-curl --with-swf=./dist/ --with-imap-ssl --enable-xslt --with-xslt-sablot --with-mm --with-apxs=/usr/sbin/apxs --with-interbase=/opt/interbase i586-suse-linux
Does the same thing with or without i586-suse-linux, so what is it for?
Art
Jyry Kuukkanen wrote:
On Thu, 20 Feb 2003, Art Fore wrote:
Apache is OK with PHP as I can connect to a postgresql database with it via webadmin and via phrojekt. Have not found anyway to get the interbase.so or to comile it from source. When I compiled it from source, then Apache could not find it as could nothing else. (I uninstalled the SuSE PHP before this).
I installed the SuSE PHP4 again along with the php-devel, and tried to create the interbase.so file per an email from the ibsupport mail list, still does not work I guess because SuSE has bastardized it so much. Tried many suggestions, none work for one reason or another including the apxs which does not exist.
If I install the source files from php.net and compile, how do I get anything else to find the damned thing (php that is)?
Art
Hello again :-)
While you have the Suse PHP and Apache installed, write and test a little PHP script, say, test.php: <? echo phpinfo(); ?>
Now, place it somewhere in your test site and have a look at it with your browser. It will print you a page with all sorts of information on PHP. Take a look at "Configure Command" - that includes the ./configure line that the Suse mod_php was compiled with.
So, download the latest and greatest of PHP, unpack it, use the configuration command printed by phpinfo and add your Interbase option to the end, make & make install.
Then you need to restart your Apache. Have another look at your marvellous test.php and it should print information of your newly build mod_php.
It might be a good idea to save the phpinfo configuration command to a file, say, "phpconf":
#!/bin/sh ./configure --prefix=/some/suse/place etc....
This way it is safer than using phpinfo page, as your Apache might be down and cannot be started.
I hope this helps.
Cheers, --jq
Jyry Kuukkanen wrote:
On Tue, 18 Feb 2003, Art Fore wrote:
How can I install the php-interbase extension with PHP? I have found no options for that in YAST and if I compile it from source from php.org with the option, it is not recognized by Apache. SuSE intalls it in /usr/share/php and the source installs it in /usr/local/lib/php.
Hello
Many applications, when compiled from source, installs by default under /usr/local/appname, but practically all distributors, such as Suse, does not like this approach that much. Distributions often install, say, Apache, into several folders: executable goes under /usr/sbin, libraries under /usr/lib, configuration files under /etc and so on.
Now, if you compile and install www.php.net version of PHP yourself, and if you want to have it installed with Apache installed by Suse's Yast, you have to specify these folders where configuration and Apache modules go.
I have done this with Suse 7.3 once, to test the procedure out, but otherwise I have always compiled both Apache and PHP from source by myself, as I have found it easier to manage.
Another thing is, that you better remove the mod_php.rpm installed by Suse Yast before compiling & installing this new PHP, as next time Suse makes update for mod_php available, it naturally installs it over your copy.
Compiling Apache and PHP to support Interbase is fairly trivial.
Apache (1.3.x): ./configure --enable-module=so make; make install
PHP4.x: ./configure --with-apxs=/usr/local/apache/bin/apxs \ --with-interbase/path/to/interbase --with-mysql (and so on with other opts) make; make install
Then you have to modify the httpd.conf under /usr/local/apache/conf to load the mod_php by LoadModule and associate .php with that module. This is explained in PHP's INSTALL file.
If you need more help, mail to this or suse-linux-e list.
Cheers,
-- --Jyry :-( C:-/ C========8-O C8-/ C:-(
participants (2)
-
Art Fore -
Jyry Kuukkanen