Re: php4 + postgresql

[Anil Madhavapeddy <anil@recoil.org>]

On Thu, May 08, 2003 at 10:34:32PM -0400, alex avriette wrote:
> >Well, give me a sparc64, and I'll make php work on it.  sorry,
> >i cant fix bugs on architectures I dont have access to (and no,
> >an account doesnt count).
> 
> I offered to send an Ultra 1 to Margarida, but when I found out what 
> the shipping to Spain was, that was nixed. You can get an Ultra 1 
> yourself for $65 if you're so inclined, talk to my pal John Butler at 
> anysystem.com. It is reasonably fast (certainly fast enough to compile 
> php all day long), and has enough room for ram, disk and other goodies. 
> Although I have no idea why you need physical access to a machine to 
> port php.

I need to use php to port it.

> >It's already fixed in -current for about a week.  I'm tempted to mark
> >the PHP port broken on sparc64 since there have been so many clear
> >breakage reports on it (anyone using it successfully?)
> 
> That would be silly. Fix the port. The PHP folks acknowledge it is 
> broken (4.3.1) on 64-bit machines. This is fixed in their 
> stable-current (what awful nomenclature) tree. I downloaded 
> php4-STABLE-200305082130 today, and except for the sha1.c problem 
> (using -O vs -O2), it compiled beautifully, and I have it running in 
> the apache chroot jail right now. This strikes me as very easy to fix 
> in the makefile, with the exception of having to move to the 
> stable-current branch. Maybe you should ping wez@php.net about this.

You seem to be making an awful lot of assumptions.  It's a huge
switch from -current to the -stable branch, certainly just for
one architecture.  If it strikes you as very easy to fix in the Makefile,
I urge you to give me a -stable patch. 

> >as for chrooted httpd, php in 3.3 works pretty well with it,
> 
> (if you can compile it)

On sparc64; works fine everywhere else.  And looks to me as if
3.3 has a php4-core-4.2.3p1 package available; have you tried that?

> >In 3.4, a bunch of the work will already be done (pear installs
> >under the chroot, sets up the php include path correctly so it
> >work in both the chroot/non-chroot automatically).
> 
> Let me get this straight. The 3.4 port is working but the 3.3-current 
> one has issues?

Sigh ...

> I'm not familiar with the restart problem you're talking about here. 
> Did I miss something?

Yes ... 

Anil