Re: Creating an extra library
| From: | Tom Vandeplas | Date: | Tue, 07 Jan 2003 09:52:28 +0000 |
| Subject: | Re: Creating an extra library | ||
| References: | 1 2 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-130550@lists.php.net to get a copy of this message | ||
Hi J,
this is exactly the information I'm looking for, unfortunately the phpize or
pear scripts are not in the 4.2.2 distribution. Is this feature removed from
the newer distributions?
However I found the scripts on the web but they gave quite some errors:
when the script runs autoconf I get "error: m4_defn: undefined macro:
_m4_divert_diversion"
maybe the versions are incompatible?
Any Ideas ?
Thx, Tom
"J Smith" <dark_panda@hushmail.com> wrote in message
news:20030106175236.15289.qmail@pb1.pair.com...
>
> Since there's no PHP XSLT extension RPM from Red Hat (as far as I can
tell),
> the easiest way to build it would probably be...
>
> 1. download the PHP source code.
>
> 2. in the ext/xslt directory, run phpize. This is assuming the Red Hat RPM
> installed PEAR and it's utilities.
>
> 3. Run ./configure, make, make install, etc. on the XSLT directory to
build
> your xslt.so shared object.
>
> 4. Modify php.ini to load the new extension, or use the dl() function in
> your scripts.
>
> Of course, you'll also have to install Sablotron and such as well...
>
> J
>
>
> Tom Vandeplas wrote:
>
> > Hi all,
> >
> > this question may have been asked a couple of times already,
unfortunately
> > I can't find the answer.
> >
> > I have a complete PHP-webserver system up and running, based on a
standard
> > redhat PHP distribution. The only thing that is missing are the XSLT
> > funtions. I managed to build php on a different system with xslt
enabled,
> > but then again it lacks all the nice standard features that come with
the
> > redhat distribution.
> >
> > The thing I would like to do is to build "xslt.so" so I can add it to
the
> > existing setup. I know it should be possible since this is the way
RedHat
> > distributes additional libraries. Unfortunately it's not clear to me how
> > to build these "so" files or how to add them to a setup.
> >
> > Any help on this would be greatly appreciated.
>