Hello Jeff,
Thursday, February 3, 2005, 11:18:40 PM, you wrote:
> On Thu, 3 Feb 2005, Derick Rethans wrote:
>> > > > Is this a deliberate change? Is there some way to tell configure to
>> > > > use the system snprintf instead of the PHP version?
>> > >
>> > > You should always been using the ap_
On Thu, 3 Feb 2005, Derick Rethans wrote:
> > > > Is this a deliberate change? Is there some way to tell configure to
> > > > use the system snprintf instead of the PHP version?
> > >
> > > You should always been using the ap_php_snprintf() one as that has an
> > > extra modified %F for non-locale
On Thu, 3 Feb 2005, Jeff Olhoeft wrote:
> > > Is this a deliberate change? Is there some way to tell configure to
> > > use the system snprintf instead of the PHP version?
> >
> > You should always been using the ap_php_snprintf() one as that has an
> > extra modified %F for non-locale aware numbe
On Thu, 3 Feb 2005, Jeff Olhoeft wrote:
> Hello,
>
> We recently upgraded a system from PHP 4.3.4 to 4.3.10, and tripped
> over a problem with snprintf. One of our PHP extension modules
> started failing, causing Apache to exit with code 0177. Investigation
> showed the culprit to be snprintf. I
Hello,
We recently upgraded a system from PHP 4.3.4 to 4.3.10, and tripped
over a problem with snprintf. One of our PHP extension modules
started failing, causing Apache to exit with code 0177. Investigation
showed the culprit to be snprintf. It turns out that in 4.3.10,
snprintf is #defined to
