RE: Updated HOWTO [Re: Linux target, cygwin host ]

["Fabrice Gautier" <gautier at email dot enst dot fr>]

> -----Message d'origine-----
> De : crossgcc-owner@sources.redhat.com
> [mailto:crossgcc-owner@sources.redhat.com]De la part de Mumit Khan
> Objet : RE: Updated HOWTO [Re: Linux target, cygwin host ]
>
> On Thu, 25 Jan 2001, Fabrice Gautier wrote:
>
> First of all, GCC is GNU Compiler Collection, and you sound like you're
> talking about only the *C* compiler which is part of GCC. So assuming
> that you're only talking about the C compiler, you're correct that you
> don't need the target includes/libraries to build xgcc/cc1 (the compiler
> driver and the backend compiler respectively), but there's one slight
> problem in building libgcc.a, which is built when you build the C
> compiler. Unless the "inhibit_libc" macro is defined, GCC will try to
> look for and include stdio.h and unistd.h. If you looked in libgcc2.c,
> this would have been apparent. GCC's configure defines this macro when
> you use --with-newlib at configure time. In this case, you can build
> the C compiler and libgcc2 without any target includes or libraries.

Yep, in fact it's exactly what you have to do when building the toolchain
for eCos: the instructions are --with-newlib and LANGAGES="c c++"
(even if eCos doesn't use newlib)

> I hope this explains the issues in some detail, the rest is up to you.

Thanks, it worked.

--
Fabrice Gautier
gautier@email.enst.fr




------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com