This is the mail archive of the
newlib@sources.redhat.com
mailing list for the newlib project.
Re: Compiling with newlib headers?
- To: "Russ.Shaw" <russell at webaxs dot net>, <gcc-help at gcc dot gnu dot org>, <crossgcc-help at sourceware dot cygnus dot com>, <newlib at sources dot redhat dot com>
- Subject: Re: Compiling with newlib headers?
- From: "Tim Prince" <tprince at computer dot org>
- Date: Fri, 29 Sep 2000 06:03:26 -0700
- References: <956378151.11400.ezmlm@gcc.gnu.org> <39D44B80.45F9D1D1@webaxs.net>
OK, can anyone confirm or correct me?
The headers are needed when running configure. They can be copied into the
target build directory in /include; if they are somewhere else,
"with-headers" is required to point to them. The same situation may arise
even when building a new copy of gcc where host==target.
----- Original Message -----
From: "Russ.Shaw" <russell@webaxs.net>
To: <gcc-help@gcc.gnu.org>; <crossgcc-help@sourceware.cygnus.com>;
<newlib@sources.redhat.com>
Sent: Friday, September 29, 2000 12:57 AM
Subject: Compiling with newlib headers?
> Hi all,
>
> 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?
>
>
> --
> *******************************************
> * Russell Shaw, B.Eng, M.Eng(Research) *
> * email: russell@webaxs.net *
> * Victoria, Australia *
> *******************************************