This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Re: How do I point out OS includes? -- Or how to Build My Own SDK using Newlib
- From: "Jonathan S. Shapiro" <shap at eros-os dot com>
- To: Duane Ellis <duane at duaneellis dot com>
- Cc: Anders Lindgren <ali at df dot lth dot se>, newlib at sourceware dot org
- Date: Fri, 13 Apr 2007 14:33:19 -0400
- Subject: Re: How do I point out OS includes? -- Or how to Build My Own SDK using Newlib
- References: <Pine.GSO.4.60.0704131150430.4637@igloo.df.lth.se> <461F92F6.1060003@duaneellis.com>
On Fri, 2007-04-13 at 10:25 -0400, Duane Ellis wrote:
> You did not say _which_ OS you are using... I'll assume you have your
> own Custom OS
> (I see Jonathan was involved with Eros-Os..)
>
> If _YOUR_ OS is linux, go seach for "crosstool", it is a great solution.
>
> perhaps I should make a "Non-Linux" Cross tool solution.
I don't know what Anders is building. In our case we are targeting
Coyotos (the EROS successor), and this is a big mess.
glibc is now hopelessly linux-dependent. My impression is that they gave
up on OS portability a long time ago. This is why we use newlib :-)
The C++ concern is that stdlibc++ appears to depend on a number of
things in libc that are linux- or POSIX-dependent as well. In many cases
I would be happy to just remove those parts of stdlibc++ (e.g. time
formatting).
If you were inclined to set up a non-linux crosstool scheme, we might be
willing to pay you to do it. My immediate question is: do you know
someplace where there is an existing howto for non-linux g++
cross-build, or can you provide some hints to us?
Happy to pick this up by phone if you like -- drop me an email
individually. At the very least, I'll be happy to write up whatever we
eventually get working so that others will have a hint of where to
start.
shap