This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: fix build problem on SunOS 4.1.4
- To: toon at moene dot indiv dot nluug dot nl, zackw at stanford dot edu
- Subject: Re: fix build problem on SunOS 4.1.4
- From: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Date: Fri, 24 Nov 2000 10:22:16 -0500 (EST)
- Cc: gcc-patches at gcc dot gnu dot org, mrs at windriver dot com
> From: "Zack Weinberg" <zackw@stanford.edu>
>
> On Wed, Nov 22, 2000 at 10:55:36PM +0100, Toon Moene wrote:
> > Kaveh R. Ghazi wrote:
> >
> > > Curious, were there any other problems? E.g. when testing with
> > > bootstrapping with gcc -traditional on solaris I have horrible
> > > problems building the fortran docs. (The fortran doc creation use
> > > some gimicky C tricks making use lots of ANSI'isms. They are now
> > > always built regardless of the LANGUAGES variable which torpedoes
> > > stage1 K&R compilers.)
> >
> > Sigh - the stuff in the f/ directory was never written with the prospect
> > in mind that it would have to conform to K&R I syntax / semantics ...
>
> Couldn't we just change the rule so it uses the just-built C compiler?
> In a cross compilation you'd have to have an ANSI compiler, but you
> need that anyway.
> zw
Probably. I take it you mean that we would use xgcc in native but
HOST_CC otherwise? Do you have a suggestion on how to switch on that
and achieve it?
Also, I don't recall the reason an ANSI compiler is required for cross
compilation. What was that again?
Thanks,
--Kaveh
--
Kaveh R. Ghazi Engagement Manager / Project Services
ghazi@caip.rutgers.edu Qwest Internet Solutions