, August 17, 2002 5:44 AM
> To: [EMAIL PROTECTED]
> 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 l
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 i
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 ph
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.
