Groups | Search | Server Info | Login | Register

Groups > gnu.gcc.bug > #6

Re: problem with making gcc on Sun4/SunOs 4.0

Show all headers | View raw

On Friday, November 11, 1988 at 12:56:23 AM UTC-8, Greg Onufer wrote:
> From article <4...@dmk3b1.UUCP>, by d...@dmk3b1.UUCP (David Keaton):
> > In article <881109151...@sunbar.mc.duke.edu> n...@SUNBAR.MC.DUKE.EDU (Ned Danieley) writes:
> > )make CC=stage1/gcc CFLAGS="-g -O -Bstage1/"
> > )stage1/gcc -g -O -Bstage1/ -sun4 -c toplev.c
> > )stage1/gcc: Program cc1 got fatal signal 6.
> > )*** Error code 1
> > )make: Fatal error: Command failed for target `toplev.o'
> > )I appear to have correctly followed the installation instructions;
> > )is this a bug?
> > Yes, it's a bug, but the bug is Sun's. They have changed the meaning
> > of the -B flag to cc. Their equivalent of "-Bstage1/" would be
> > "-Qpath stage1".
> No bug that I see... David is not using Sun's C compiler. -Bstage1/
> is a flag for _gcc_ to tell it where to look. Sun's CC should not be
> called anywhere at this point (using the first generation gcc to compile
> the second generation). It looks like David installed everything
> correctly so the bug may very well be in gcc. I haven't gotten a
> a trustable gcc running on the Sun Roadrunner for that matter. Gcc-1.28
> works fairly well, but only if it doesn't use __builtin_alloca (ie. It
> compiles itself with stage2/gcc with no differences in the object
> files other than in the damned COFF headers-- why did Sun have to do
> that to us? Is a binary standard _that_ important to them?). When
> using __builtin_alloca, stage2/gcc cannot compile itself (or anything
> with Optimization turned on).
> Any clues?
> --greg
> -- 
> Greg Onufer .. University of the Pacific .. Focus Semiconductor
> .. exo...@cheers.uucp .. sun!daver!cheers!exodus .. 415-965-0604
In your fudi

Back to gnu.gcc.bug | Previous | Next | Find similar

Thread

Re: problem with making gcc on Sun4/SunOs 4.0 KP KP <jungletrain@outlook.com> - 2022-08-01 16:13 -0700

csiph-web