snprintf on linux

[Brian Behlendorf <br...@hyperreal.com>]

Hmm, dunno how this should be handled.

	Brian

--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
brian@hyperreal.com     http://www.apache.org     http://www.organic.com/jobs

---------- Forwarded message ----------
Date: Mon, 27 Jan 1997 18:00:34 GMT
From: Alan Cox <al...@cymru.net>
To: apache@apache.org
Subject: snprintf


Linux libc5.2.18+ snprintf() in the C library works just nicely. In a.out
libc4 it is there but has an overrun bug

Alan Cox
Alan.Cox@linux.org

Re: snprintf on linux

[Dean Gaudet <dg...@arctic.org>]

I would guess most people use ELF 5.2.18+ systems -- all distributions
come with 5.2.18+ now anyhow.  They probably all come with 5.3.12+.  A
test like this: 

    ldd `which gcc`

Will display which c library gcc itself runs against.  The user can still
shoot themself by telling gcc to generate a.out, but that test and a
warning during configure would be sufficient.

[38]twinlark:~% ldd `which gcc`
        libc.so.5 => /lib/libc.so.5.4.17
[39]twinlark:~% ldd `which perl`
        libdb.so.2 => /usr/lib/libdb.so.2.0.0
        libgdbm.so.2 => /usr/lib/libgdbm.so.2.0.0
        libdl.so.1 => /lib/libdl.so.1.7.14
        libm.so.5 => /lib/libm.so.5.0.7
        libc.so.5 => /lib/libc.so.5.4.17

Dean

On Mon, 27 Jan 1997, Brian Behlendorf wrote:

> 
> Hmm, dunno how this should be handled.
> 
> 	Brian
> 
> --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
> brian@hyperreal.com     http://www.apache.org     http://www.organic.com/jobs
> 
> ---------- Forwarded message ----------
> Date: Mon, 27 Jan 1997 18:00:34 GMT
> From: Alan Cox <al...@cymru.net>
> To: apache@apache.org
> Subject: snprintf
> 
> 
> Linux libc5.2.18+ snprintf() in the C library works just nicely. In a.out
> libc4 it is there but has an overrun bug
> 
> Alan Cox
> Alan.Cox@linux.org
> 
> 
>