This is the mail archive of the
newlib@sources.redhat.com
mailing list for the newlib project.
Re: Compiling with newlib headers?
- To: Stefan Petters <petters at lpr dot e-technik dot tu-muenchen dot de>
- Subject: Re: Compiling with newlib headers?
- From: "Russ.Shaw" <russell at webaxs dot net>
- Date: Sat, 30 Sep 2000 09:16:54 +1000
- CC: crossgcc at sourceware dot cygnus dot com, newlib at sources dot redhat dot com
- References: <956378151.11400.ezmlm@gcc.gnu.org> <39D44B80.45F9D1D1@webaxs.net> <39D44FB6.388ABAAD@webaxs.net> <20000929102702.A21866@fozzie.lpr.e-technik.tu-muenchen.de>
Hi,
Is the path to the newlib headers just the directory that
all of newlib is under, or is it a subdirectory within this?
> configure gcc (--with-headers=<path to the newlib-headers>)
Stefan Petters wrote:
>
> Hi,
>
> Russ.Shaw wrote:
> > When compiling gcc for an embedded cpu, and newlib
> > is required, is "with-headers" needed as an option
> > to "configure gcc" ?
> >
> > Does this mean newlib should be installed before
> > gcc?
> >
> > Does the "with-headers" option need to point to
> > a directory?
> >
> > Should newlib be installed before binutils?
> >
> > Are there other ways of including newlib
> > when compiling the whole system?
> This means you should have newlib unpacked for making the compiler. You
> can't make the newlib without having a compiler, but the compiler needs
> to know, what will be in the newlib once it's done (for libgcc I
> believe).
>
> Normally it goes the following way.
>
> make binutils
> unpack newlib
> unpack gcc
> configure gcc (--with-headers=<path to the newlib-headers>)
> make gcc
> configure and make newlib.
>
--
*******************************************
* Russell Shaw, B.Eng, M.Eng(Research) *
* email: russell@webaxs.net *
* Victoria, Australia *
*******************************************