This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: printf

From: "Grant Likely" <grant dot likely at secretlab dot ca>
To: "Franzi Edo." <edo dot franzi at ukos dot ch>
Cc: crossgcc at sourceware dot org
Date: Sat, 27 May 2006 12:40:33 -0600
Subject: Re: printf
References: <5C9EF03A-B92F-40CF-A522-991D1FE93751@ukos.ch>

On 5/27/06, Franzi Edo. <edo.franzi@ukos.ch> wrote:

Hi,
I would like to implement the "printf" function on my target.
Accordingly with the documentation I found it seems that it is enough
to write some low level routine such "fstat, sbrk, istty, ... read,
write". So, I implement these functions and I can monitor that fstat,
sbrk and isatty are called during the printf. However, the write is
never called. Do I have initialise some I/O table or tuffs like this
to make operational my printf? Any ideas?

This is kind of off-topic for this list, but...

What C library are you using?  Is it using buffered IO?  If so, you
either need to turn off buffering, or call fflush() after printf().

Cheers,
g.

--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

--
For unsubscribe information see http://sourceware.org/lists.html#faq

References:
- printf
  - From: Franzi Edo.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]