This is the mail archive of the
newlib@sources.redhat.com
mailing list for the newlib project.
Re: About porting newlib to arm...
- From: "Anil Paranjape" <AnilP1 at KPITCummins dot com>
- To: <u8806228 at ms2 dot ttu dot edu dot tw>
- Cc: <newlib at sources dot redhat dot com>
- Date: Mon, 6 Sep 2004 10:18:44 +0530
- Subject: Re: About porting newlib to arm...
Hi Yen-Ting Chen,
Please refer to following link,
http://billgatliff.com/articles/newlib/newlib.pdf
This document is useful in porting newlib to any target.
Best Regards,
Anil Paranjpe
KPIT Cummins InfoSystems Ltd.
Pune, India
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Free download of GNU based tool-chains for Renesas' SH and H8 Series.
The following site also offers free technical support to its users.
Visit http://www.kpitgnutools.com for details.
Latest versions of KPIT GNU tools were released on June 1, 2004.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--------------------------------------------------------------------------------
From: Yen-Ting Chen <u8806228 at ms2 dot ttu dot edu dot tw>
To: newlib at sources dot redhat dot com
Date: Sun, 05 Sep 2004 12:08:39 +0800
Subject: About porting newlib to arm...
Dear all,
Could anyone tell me what is the difference between these directories,
and what I can make use of from these directories?
1) newlib-<version>/libgloss/arm/
2) newlib-<version>/newlib/libc/machine/arm/
3) newlib-<version>/newlib/libc/sys/arm
If I want to port newlib to arm, should I modify
newlib-<version>/newlib/libc/syscalls/*.c or just
newlib-<version>/newlib/libc/sys/arm/syscalls.c ?
And do I need to do with newlib-<version>/libgloss/arm ??
Thanks in advance.