RE: [PHP-DEV] Tru64, snprintf and bug #1298
| From: | Sebastian Nohn | Date: | Sat, 17 Aug 2002 13:36:14 +0000 |
| Subject: | RE: [PHP-DEV] Tru64, snprintf and bug #1298 | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-86942@lists.php.net to get a copy of this message | ||
Maybe U should say that I use gcc (2.9) under Tru64, the other thing is that
I've experienced most bugs also under Linux/Alpha and FreeBSD/Alpha, so I
think it's 64-bit in most cases.
> -----Original Message-----
> From: Dan Kalowsky [mailto:dank@deadmime.org]
> Sent: Saturday, August 17, 2002 5:44 AM
> To: marcus.boerger@post.rwth-aachen.de
> Cc: PHP Development Mailing list
> Subject: Re: [PHP-DEV] Tru64, snprintf and bug #1298
>
>
> Well it's starting to sound like it might be necessary to do this. While
> nohn's compiler is working, it seems that at least one other Tru64 person
> is having difficulty.
>
> Looking at the influx of bugs as well, I'm wondering if Tru64 is going to
> be more of a problem for the project as whole... or if it's just 64-bit
> arch's in the end.
>
> On Sat, 17 Aug 2002, Marcus [iso-8859-1] Börger wrote:
>
> > First of all the internal replacement of snprintf fails if size
> is 1 or 0.
> > Second it is not C99 complient and third we do not include it the
> > right way. We would need to check if snprintf is available and if it is
> > C99 complient and if not use the replacement.
> >
> > I had a lengthy discussion with the php group on that but i did
> > not get any answer at last. This might be the case because my
> > first worst assumptions were wrong for most systems.
> >
> > In fact i could commit detection code and corect replacement code
> > but will do only when receiving a go from the group.
> >
> > regards
> > marcus
> >
> > At 23:31 16.08.2002, Dan Kalowsky wrote:
> > >Yes, that is correct, bug #1298 (it's existed for a LONG time).
> > >
> > >The user is having some difficulty compiling the Zend
> libraries for 4.2.2.
> > >Mainly it seems that snprintf is turning up as an unresolved symbol.
> > >I asked him to grep through the /usr/include looking for it, and the
> > >result was nothing.
> > >
> > >Looking through the code I see PHP has it's own snprintf
> implementation,
> > >and that should suffice. Apparently zend_API.c though doesn't
> notice it.
> > >His fix was to place <#include "php.h"> inside the file, and
> > >everything
> > >worked fine.
> > >
> > >Does anyone have any more insight into this that they might be able to
> > >share?
> > >
Regards,
Sebastian Nohn
--
+49 170 471 8105 - sebastian@nohn.net - http://www.nohn.net/
PGP Key Available - Did I help you? Consider a gift:
http://www.amazon.de/exec/obidos/wishlist/3HYH6NR8ZI0WI/