Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:14594 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 45555 invoked by uid 1010); 3 Feb 2005 20:53:48 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 45531 invoked from network); 3 Feb 2005 20:53:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Feb 2005 20:53:48 -0000 X-Host-Fingerprint: 212.204.192.51 jdi.jdimedia.nl Linux 2.5 (sometimes 2.4) (4) Received: from ([212.204.192.51:48340] helo=jdi.jdimedia.nl) by pb1.pair.com (ecelerity HEAD (r4105:4106)) with SMTP id F9/43-10528-B5F82024 for ; Thu, 03 Feb 2005 15:53:48 -0500 Received: from localhost (localhost [127.0.0.1]) by jdi.jdimedia.nl (8.12.11/8.12.11) with ESMTP id j13KrjC2013275 for ; Thu, 3 Feb 2005 21:53:45 +0100 Received: from jdi.jdimedia.nl ([127.0.0.1]) by localhost (jdi.jdimedia.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 12698-04-2 for ; Thu, 3 Feb 2005 21:53:45 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by jdi.jdimedia.nl (8.12.11/8.12.11) with ESMTP id j13KrDvH013210; Thu, 3 Feb 2005 21:53:14 +0100 Date: Thu, 3 Feb 2005 21:53:14 +0100 (CET) X-X-Sender: derick@localhost To: Jeff Olhoeft cc: PHP Developers Mailing List In-Reply-To: <000401c50a31$c9c25a80$54160a0a@ATLANTIC> Message-ID: References: <000401c50a31$c9c25a80$54160a0a@ATLANTIC> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at jdimedia.nl Subject: RE: [PHP-DEV] snprintf defined as ap_php_snprintf From: derick@php.net (Derick Rethans) 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 number formatting. To make your > > extension work, make sure to include main/snprintf.h. > > I'm afraid I might not have been clear. In 4.3.10, php.h includes > snprintf.h, which defines snprintf as ap_php_snprintf. Unfortunately, > ap_php_snprintf is failing, causing the module to crash. If I force it to > use glibc's snprintf, everything works fine. Unfortunately, ap_php_snprintf > isn't an option right now, and I'm wondering what is the cleanest way to > insure that the system snprintf is used. You can't do that actually. What fails in ap_php_snprintf? We need to fix that instead. (And always CC the mailinglist). regards, Derick -- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org