Newlib Linux Port
Mon Nov 28 17:23:00 GMT 2005
I'm working on a similar project. My first step was to make
i386-linux-newlib accepted as a first-class target by config
(config.guess, config.sub, configure, libtool, and others). See "Add
linux-newlib to config [PATCH]" posted on 2005-11-15.
On the topic of external headers, you should read "External headers
required for i386-linux-newlib" posted on 2005-11-16.
I'm eventually aiming towards an arm-linux-newlib port. This is not a
small undertaking though. You might want to consider looking into
uClibc, which already targets Linux.
2005/11/25, Matt Kern <email@example.com>:
> Hello, all.
> I am currently working on a project to port linux to a new system-on-chip.
> We are at the point where we have the port up and running and are now
> refocussing on the user-space side of things. We have a newlib build that
> works with libgloss on the bare metal, but we would like to make newlib our
> native linux C library.
> I've taken a couple of days to look over the newlib source and made a first
> stab at a port by creating a minimal setup, and iteratively cross-compiling
> it and fixing up the errors. I've run into a few problems that I would like
> clarification on:
More information about the Newlib