All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erik Christiansen <erik@dd.nec.com.au>
To: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Cc: Ron Flory <ron.flory@adtran.com>
Subject: Re: embedded gcc PPC toolchain questions
Date: Mon, 2 Jun 2003 16:26:56 +1000	[thread overview]
Message-ID: <20030602062656.GD833@dd.nec.com.au> (raw)
In-Reply-To: <20030529162243.ED346C5492@atlas.denx.de>


in message <3ED6298C.3070901@adtran.com> Ron Flory wrote:

> 4.  I know the question of embedded libc comes up often.  For
>     the most part, we basically need the 'strxxx' and 'memxxx'
>     functions, but 'sprintf' is quite a different critter.  Since
>     we are running an 860, we won't have FP support (and we don't
>     want to deal with emulation).  Do most folks use a hand-patched
>     'sprintf' source file, manually removing the floating-point ops?
>     I've looked into this a few years ago (the gcc sprintf source
>     file is a horror).  Has the 'ulibc' that i've heard about been
>     used with success by anybody on this list for embedded non-linux
>     projects?

Ron,

   We're happily using newlib's sprintf on the mpc850, in a piece of
   seriously embedded non-linux equipment.

   According to my rough notes, µClibc is LGPL, so static linking may not
   be a good idea. Newlib's BSD-like terms seemed more appealing to me.

   http://sources.redhat.com/newlib

   Bill Gatliff wrote an article on it, in the December 2001 issue of
   Embedded Systems Programming.

   There's apparently also dietlibc and sglibc, but I haven't
   investigated either.

Regards,
Erik


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-06-02  6:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-19 22:47 linux-embedded: smallest kernel for 2.4.0-test9 Brendan J Simon
2000-10-20  2:07 ` Dan Malek
2003-05-29 15:38   ` embedded gcc PPC toolchain questions Ron Flory
2003-05-29 16:22     ` Wolfgang Denk
2003-06-02  6:26       ` Erik Christiansen [this message]
     [not found] <5.1.0.14.2.20030529125224.03782278@falcon.si.com>
2003-05-29 18:56 ` Ron Flory
2003-05-29 20:21   ` Wolfgang Denk
     [not found] <F0B628F30F48064289D8CCC1EE21B7A80C4884@mvebe001.americas.nokia.com>
2003-05-30  7:41 ` Wolfgang Denk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030602062656.GD833@dd.nec.com.au \
    --to=erik@dd.nec.com.au \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=ron.flory@adtran.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.