RE: Printf doesn't result in a call to write

["Matt Gessner" <mgessner at Avidyne dot com>]

OK, before I start flooding the list with all of the replies to your
good replies, where can I read more on what I should supply?  The
section at the end of the manual I have says to supply write, read,
close, open, sbrk, etc and the *implication* is that it will work.

Thank you in advance,

Matt

> -----Original Message-----
> From: newlib-owner@sourceware.org [mailto:newlib-owner@sourceware.org]
On
> Behalf Of Shaun Jackman
> Sent: Monday, September 11, 2006 12:40 PM
> To: Matt Gessner
> Cc: newlib@sourceware.org
> Subject: Re: Printf doesn't result in a call to write
> 
> Hello Matt,
> 
> On many targets (all targets?), printf calls the function _write, not
> write.
> 
> Cheers,
> Shaun
> 
> On 9/11/06, Matt Gessner <mgessner@avidyne.com> wrote:
> >
> > Hi, all,
> >
> > I'm using gcc 4.1.1 and newlib 1.14
> >
> > I've supplied appropriate write(), open(), etc calls for my
powerpc-eabi
> > host.
> >
> > I've found that calling printf with a string results in a call to
puts,
> > but somehow, write() is never getting invoked.  Can someone suggest
what
> > I've done wrong or what I need to do?
> >
> > I've not written any of the _r routines.  Also, I can't find any
> > reference to any library startup I need to invoke when my
application
> > comes up (it's a completely standalone app -- no OS, simply ISR's
and
> > application code).
> >
> > Would someone please advise?
> >
> > Thanks,
> >
> > Regards,
> >
> > Matt Gessner