This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
RE: Printf doesn't result in a call to write
- From: "Matt Gessner" <mgessner at Avidyne dot com>
- To: "Dave Korn" <dave dot korn at artimi dot com>
- Cc: <newlib at sourceware dot org>
- Date: Mon, 11 Sep 2006 12:39:23 -0400
- Subject: RE: Printf doesn't result in a call to write
I was under the impression that the \n character at the end would bypass
that.
I'll add an fflush to stdout to see if that helps.
Good point, though...
> -----Original Message-----
> From: newlib-owner@sourceware.org [mailto:newlib-owner@sourceware.org]
On
> Behalf Of Dave Korn
> Sent: Monday, September 11, 2006 12:39 PM
> To: Matt Gessner; newlib@sourceware.org
> Subject: RE: Printf doesn't result in a call to write
>
> On 11 September 2006 17:32, Matt Gessner 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?
>
> Read up about "stdio buffering" ?
>
> > Would someone please advise?
>
> Check the advice in
http://sourceware.org/ml/newlib/2006/msg00470.html
> and
> let us know if it helps any.
>
>
> cheers,
> DaveK
> --
> Can't think of a witty .sigline today....