[uClibc] libsafe does not build against uClibc
Erik Andersen
andersen at codepoet.org
Tue Oct 12 21:12:07 UTC 2004
On Tue Oct 12, 2004 at 06:09:26PM +0200, Peter S. Mazinger wrote:
> On Tue, 5 Oct 2004, Erik Andersen wrote:
>
> > On Tue Oct 05, 2004 at 10:45:24AM +0200, Peter S. Mazinger wrote:
> > > Hello!
> > >
> > > Trying to build libsafe it misses _IO_vfscanf? Has someone managed to
> > > build it against uClibc?
> > > Would it be correct to replace _IO_vfscanf w/ vfscanf?
> >
> > _IO_vfscanf is a glibc internal function. _IO_vfscanf and
> > vfscanf implement the same function but have different function
> > prototypes:
> >
> > int _IO_vfscanf (_IO_FILE *s, const char *format, _IO_va_list argptr, int *errp)
> > int vfscanf (FILE *s, const char *format, va_list argptr)
> >
> > Whatever libsafe is doing (presumably replaceing vfscanf to check
> > for buffer overflows), it is clearly being extra friendly with
> > glibc,
>
> Attached a patch for libsafe to be used w/ uClibc.
Ugh. You can't be serious? Emulating glibc libio internals
that libsafe should not be using?
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
More information about the uClibc
mailing list