glibc vs. newlib

[Erik Christiansen]

On Fri, Apr 04, 2003 at 07:30:21PM -0600, Mark Hatle wrote:
> I strongly recommend you stay away from newlib.

Mark,

   Is it something related to linux that has given you a bad experience
   with newlib? (There is no related information in your post, so I'm
   curious.)

   We are using newlib on a bare-bones ppc board, with every success.
   We've trialled the library in both dynamically relocatable form, and
   statically linked.

   An exerpt from the cross-gcc FAQ helps clarify when you might use it:
>>>
   Licensing
      Glibc is covered by the LGPL (the GNU Library General Public License).
   Newlib is a collection of software from several sources, each with their own
   copyrights, but basically it's a Berkeley style copyright.

   Resource Utilization
      Glibc, being intended for native Unix environments, does not need to worry
   about memory usage as much. It is designed to work most efficiently in
   demand-page-loaded shared library situations. Newlib, being intended for
   embedded systems, does worry about memory usage (and is more memory-efficient
   than glibc).
<<<

Regards,
Erik


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