This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: g77's use of assert and x-compilation
- To: khan at xraylith dot wisc dot edu
- Subject: Re: g77's use of assert and x-compilation
- From: Ian Lance Taylor <ian at cygnus dot com>
- Date: Wed, 22 Jul 1998 11:08:33 -0400
- CC: law at cygnus dot com, egcs at cygnus dot com
Date: Wed, 22 Jul 1998 00:18:35 -0500 (CDT)
From: Mumit Khan <khan@xraylith.wisc.edu>
My solution currently is one of two:
a. use local patches that take out the forced-definition of inhibit_libc
in libgcc2.c. Since my targets come with full set of headers, it's
not an issue. This IMO should only be done for real embedded
targets. I remember way back when this macro was added by Cygnus
top-level configure if target was using newlib.
b. After building the cross-compiler, use that to build *only* the
native* C compiler so that libgcc.a is built; use that to replace
the one built for the cross-compiler in Step 1 and continue on with
the rest of the languages and target libraries.
For cygwin32, we just arranged to provide __eprintf in newlib, so that
all cases were covered.
Ian