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

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 doesn't result in a call to write

From: "Shaun Jackman" <sjackman at gmail dot com>
To: "Matt Gessner" <mgessner at avidyne dot com>
Cc: newlib at sourceware dot org
Date: Mon, 11 Sep 2006 10:40:10 -0600
Subject: Re: Printf doesn't result in a call to write
References: <131AF8573CF31945B5B11E4201D3F1E142B9D4@mail3.Avidyne.com>
Reply-to: "Shaun Jackman" <sjackman at gmail dot com>

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

References:
- Printf doesn't result in a call to write
  - From: Matt Gessner

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