File	Date	Author	Commit
doc	2011-10-24	Peter A. Bigot	[a2da19] Merge branch 'scratch' into dev
include	2012-07-16	Peter A. Bigot	[292e92] Regenerate
src	2012-07-16	Peter A. Bigot	[292e92] Regenerate
.gitignore	2011-08-09	Peter A. Bigot	[68b41c] Minimal support for configuring build system wi...
.version	2012-07-16	Peter A. Bigot	[d50f4f] Update version number and release notes
COPYING	2012-07-15	Peter A. Bigot	[eac45c] Separate asctime and ?ettimeofday from time
README	2012-01-10	Peter A. Bigot	[bf09c2] Add a warning about libfp.a being untrusted
RELEASES.TXT	2012-07-16	Peter A. Bigot	[d50f4f] Update version number and release notes
configure	2012-07-03	Peter A. Bigot	[e74645] Independently control 20-bit and 32-bit printf ...

Read Me

This directory contains source code for a version of libc specifically
intended for use on the TI MSP430 microcontroller family, in conjunction
with mspgcc.

This material was collected over several years from a variety of sources.
Licensing information can be found in the file COPYING.

The development project for msp430-libc is
https://sourceforge.net/projects/mspgcc; the development repository is:

	git://mspgcc.git.sourceforge.net/gitroot/mspgcc/msp430-libc

You should ensure you have msp430 versions of binutils and gcc installed.
You should also obtain the current msp430mcu release from the mspgcc
project; this provides headers for each of the microcontrollers in the
MSP430 product line.

There is a crude configuration script that must be run to update the
Makefile and a header that defines feature presence.  Run

  ./configure --help

to see a list of options.  Until we get around to converting this to
autoconf, build with:

  ./configure
  cd src
  make
  make PREFIX=/path/to/mspgcc/installation install

The PREFIX path should be the same as the --prefix you provided when
building binutils and gcc.

** WARNING: msp430-libc provides some replacement softfloat libraries in
   libfp.a, which are significantly smaller than the ones gcc provides in
   libgcc.a, but which do not necessarily behave "correctly" even with
   IEEE754 flags enabled.  Because gcc releases may change the semantics or
   names of these internal functions, relying on libfp to replace them is a
   risky step.  libfp is user-contributed code and remains in msp430-libc
   solely for historical reasons.

** Please report all problems with this toolchain on the mspgcc bug tracker
   at:

  http://sourceforge.net/tracker/?group_id=42303&atid=432701