This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: New in newlib and porting

From: Jeff Johnston <jjohnstn at redhat dot com>
To: Sergio <hardmaker at gmail dot com>
Cc: newlib at sources dot redhat dot com
Date: Fri, 07 Jan 2011 17:56:24 -0500
Subject: Re: New in newlib and porting
References: <AANLkTikQL19bo=topka5scV2wuP+7vc+WzWN-PaXMb+x@mail.gmail.com> <AANLkTin1Wu6Q+Ng1xneKy0TQageqe1g7KqJq11bQpmGj@mail.gmail.com>

On 01/07/2011 04:23 PM, Sergio wrote:

Hi list.
I'm new in newlib and I'm trying to port newlib 1.18 to specific
hardware (embbedded without operation system).
In google I find 2 alternatives:
1) Add syscalls.c to my project with my own version of some functions
like _sbrk.
2) Use libgloss to make the port.
Before reading about 2 alternatives, I think the correct options is
the number 2. But .... where can I read how?
I'm using gcc 4.4.4 on ARM, and compile newlib with standard options
and --disable-newlib-supplied-syscalls
Other question: I have my own linker script (for my specific board and
processor) what I need to add to make
newlib work?

Thank's a lot

Sergio

Yes option 2 is the correct way to do things now.

Take a look at:
http://www.embecosm.com/appnotes/ean9/ean9-howto-newlib-1.0.pdf

If you have a linker script, that goes in libgloss as well. Take a look at libgloss/mn10300 for example which provides a sim.ld linker script to link for the simulator.

-- Jeff J.

References:
- New in newlib and porting
  - From: Sergio

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]