Edin Kadribasic wrote:
>>But one thing I know.
>>
>>If you try to compile --with-pcntl now, and you use
>>--with-apxs, the ./configure process tries to be smart and
>>bails out, saying that pcntl does not work with apache sapi.
>>
>>Seems we need some more smart changes to the
Edin Kadribasic wrote:
> What is wrong with adding a third parameter to PHP_EXTENSION? If you take a
> look at the patch, you will see that I need to create a list of libraries
> that is only built with cli. I don't know how to do that with the two macros
> you added.
you tie ext/pcntl to a
Edin Kadribasic wrote:
>>>What is wrong with adding a third parameter to PHP_EXTENSION? If you
>>>
> take a
>
>>>look at the patch, you will see that I need to create a list of
>>>
> libraries
>
>>>that is only built with cli. I don't know how to do that with the two
>>>
> macros
>
>>>you adde
Edin Kadribasic wrote:
>>i'm alread expecting bug reports regarding "my apache module doesn't have
>>extension xyz although i configured it ..."
>>
>
> Come on, give our users some credit :) I think that concept of extension's
> that work only with cli shouldn't be too difficult to grasp.
have
> wasn't the reason for having a CLI build in parallel
> with the requested SAPI to use it for bootsraping and
> things? or did i get something wrong here? might well
> be so, haven't paid as much attention to the lists
> as i should have for the last three weeks or so ... :(
Yes it was. But then
> > building say apache module and cli at the same time with some extensions
> > that are available in interactive mode only. With my proposed extension
to
> > PHP_EXTENSION the build becomes "smart" in that it links those
extensions
> > only with the cli, and not with the other api selected with
> > What is wrong with adding a third parameter to PHP_EXTENSION? If you
take a
> > look at the patch, you will see that I need to create a list of
libraries
> > that is only built with cli. I don't know how to do that with the two
macros
> > you added.
>
> you tie ext/pcntl to a certain sapi alth
> > This is bit dirty, but if you apply this patch it would enable any
extension
> > that has PHP_EXTENSION(ext_name, $ext_shared, cli) in their config.m4 to
be
> > linked only with the cli executable. The patch also modifies
> > ext/pcntl/config.m4 to make use of this.
>
> this was what i added P
> > > If you try to compile --with-pcntl now, and you use
> > > --with-apxs, the ./configure process tries to be smart and
> > > bails out, saying that pcntl does not work with apache sapi.
> > >
> > > Seems we need some more smart changes to the build process.
> >
> > This is bit
On Sun, Jan 13, 2002 at 03:00:53AM +0100, Edin Kadribasic wrote :
> > But one thing I know.
> >
> > If you try to compile --with-pcntl now, and you use
> > --with-apxs, the ./configure process tries to be smart and
> > bails out, saying that pcntl does not work with apache sapi.
>
> But one thing I know.
>
> If you try to compile --with-pcntl now, and you use
> --with-apxs, the ./configure process tries to be smart and
> bails out, saying that pcntl does not work with apache sapi.
>
> Seems we need some more smart changes to the build process.
This is b
On Sun, Jan 13, 2002 at 12:06:58AM +0100, Edin Kadribasic wrote :
> > It works with and without your latest CVS commit (and PM you
> > sent me) as long as you do make && make install and not just
> > make install (as I'm always doing it). Still not a good idea
> > .. but I'm not r
> It works with and without your latest CVS commit (and PM you
> sent me) as long as you do make && make install and not just
> make install (as I'm always doing it). Still not a good idea
> .. but I'm not ranting, I'm glad we've cli now :)
I'm learning about the php build system
On Sat, Jan 12, 2002 at 11:51:24PM +0100, Edin Kadribasic wrote :
> > > > > > I have just commited those changes. I would appreciate if people
> > > > tried
> > > > > > building PHP on their own platform and see if the build still
> works.
> > > > > >
> > > > > > Tested so far:
> > > > > > RadH
> > > > > I have just commited those changes. I would appreciate if people
> > > tried
> > > > > building PHP on their own platform and see if the build still
works.
> > > > >
> > > > > Tested so far:
> > > > > RadHat Linux 6.2
> > > > > FreeBSD 4.4-STABLE
> > > >
> > > > Trying on debian
> > > > I have just commited those changes. I would appreciate if people
> > tried
> > > > building PHP on their own platform and see if the build still works.
> > > >
> > > > Tested so far:
> > > > RadHat Linux 6.2
> > > > FreeBSD 4.4-STABLE
> > >
> > > Trying on debian unstable with late
On Sat, Jan 12, 2002 at 09:07:22PM +0100, Marcel Beerta wrote :
> Hi,
> > > I have just commited those changes. I would appreciate if people
> tried
> > > building PHP on their own platform and see if the build still works.
> > >
> > > Tested so far:
> > > RadHat Linux 6.2
> > > FreeBSD 4.4-S
Hi,
> > I have just commited those changes. I would appreciate if people
tried
> > building PHP on their own platform and see if the build still works.
> >
> > Tested so far:
> > RadHat Linux 6.2
> > FreeBSD 4.4-STABLE
>
> Trying on debian unstable with latest CVS I get:
>
> ./configur
On Sat, Jan 12, 2002 at 03:57:09PM +0100, Edin Kadribasic wrote :
> > Here is the second part of adding cli sapi wich would be built no matter
> > what other sapi was selected. My plan is to commit it later today, unless
> > someone reviews the patch and finds some problems with it.
> >
> > There
> Here is the second part of adding cli sapi wich would be built no matter
> what other sapi was selected. My plan is to commit it later today, unless
> someone reviews the patch and finds some problems with it.
>
> There is one known problem. If you select cgi sapi, make install we
> overwrite cg
20 matches
Mail list logo
