Re: gcc 2.95 crossed from linux to i386-coff

[Brendan Simon <brendan@dgs.monash.edu.au>]

Gregory Gerard wrote:

> where do I get said headers?

That I'm not sure of.  Is your i386-coff target for an embedded system ?  If so,
then newlib might have suitable headers for you.  If it is for some well known
system (eg. Win32.  Does that use coff ?  or pe-coff ?) then you will have to get
headers from the system.  Cygwin32 or Mingw32 headers may help here.  I have never
built a cross-i386 target so I can only give general advice.  Hopefully someone
else on the the CrossGCC list can give you more details.

Brendan Simon.



> ----------
> >From: Brendan Simon <brendan@dgs.monash.edu.au>
> >To: "C. M. Heard/VVNET, Inc." <heard@vvnet.com>
> >Subject: Re: gcc 2.95 crossed from linux to i386-coff
> >Date: Mon, Aug 16, 1999, 23:30
> >
>
> > "C. M. Heard/VVNET, Inc." wrote:
> >
> >> On Mon, 16 Aug 1999, Gregory Gerard wrote:
> >> >
> >> > I'm trying to build gcc 2.95 for an i386-coff target and I'm dying when it
> >> > tries to compile libgcc2.c (it can't find the header files unistd.h and
> >> > stdlib.h)
> >> >
> >> > How do I get this to work?  There is a #if directive surrounding the
> >> > inclusion of these files named inhibit_libc, but I don't know the
> >> > ramifications of forcing that flag for just that file and don't know the
> >> > correct place to turn it on in the configuration or the make.
> >>
> >> I think all you need to to is to invoke make as follows:
> >>
> >> make LANGUAGES=c GCC_CFLAGS=-Dinhibit_libc
> >>
> >> or, if you want c and c++ support, say
> >>
> >> make LANGUAGES="c c++" GCC_CFLAGS=-Dinhibit_libc
> >>
> >> At least, that was what one did back in the days of gcc-2.7.2.  Presumably
> >> someone else will chime in and correct me if this has changed.
> >
> > I'm not sure if the "LANGUAGES=" expression still works.  I have a feeling
> that
> > gcc2.95 uses the "--enable-languages=" expression as a configure argument.
> Try
> > it if the LANGUAGES expression doesn't work.
> >
> > To answer Greg's original question:
> > You must have the i386-coff headers and runtime libraries preinstalled in
> > $prefix/$target/include and $prefix/$target/lib.  An alternative is to use the
> > --with-headers option to point to the target headers.  It will then copy them
> to
> > the installation directory during the "make install" phase.
> >
> > Brendan Simon.
> >
> >


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