This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Suggestion for improving the README file
- From: rdiezmail-newlib at yahoo dot de
- To: newlib at sources dot redhat dot com
- Date: Wed, 20 Jan 2010 07:57:55 -0800 (PST)
- Subject: Suggestion for improving the README file
Hallo all:
I am a newcomer to newlib. I just downloaded and uncompressed newlib-1.18.0.tar.gz , and tried to follow the README file to build it.
It took me a while to realise that the ./configure script at the top level does very little. The Makefile it generates builds just files "configure.info" and "standards.info", and does not seem to trigger any other Makefile in any subdirectory.
After I while I discovered that you must change to the newlib/ subdirectory, in order to configure, build and install the main library. I wonder if you need the top-level configure script at all.. There is no mention about what the "libgloss" subdirectory is for either.
You can certainly work that out for yourself, but it would be nice if the README file could save you some time in that respect.
By the way, I wanted to build for an embedded PowerPC target without an OS. The processor is an MPC850, and I'm not sure which architecture name I should use. Is there some documentation about what architectures are supported and for which processors? I found rough matches like these:
powerpc | powerpc64 | powerpc64le | powerpcle | ppcbe
but I couldn't figure out which one I should specify. The WindRiver tools use parameter "-tPPC850ES:simple", this means the following: E is for "EABI", S is for "software floating point emulation", and "simple" is for "no floating point, character input/output" in the run-time libraries.
Many thanks in advance,
R. Diez
__________________________________________________
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails.
http://mail.yahoo.com