-disable-fixincludes doesn't quite work, minor

Jay K jay.krell@cornell.edu
Mon May 10 22:45:00 GMT 2010

Ok if I do both or the emails are just annoying?
I find that bugs are often ignored just as well (but not lost/forgotten, granted. :) )
 - Jay

> To: jay.krell@cornell.edu
> CC: gcc@gcc.gnu.org
> Subject: Re: -disable-fixincludes doesn't quite work, minor
> From: iant@google.com
> Date: Mon, 10 May 2010 09:50:01 -0700
> Jay K writes:
>> -disable-libgcc and/or -disable-fixincludes are useful, depending on your goal.
>> Like if you just want to compile C to assembly or object files.
>> It fails, but only after doing what I want anyway.
>> make[2]: *** No rule to make target `../build-sparc-sun-solaris2.10/fixincludes/fixinc.sh', needed by `stmp-fixinc'. Stop.
>> gmake[2]: Leaving directory `/home/jkrell/obj/gcc.sparc/gcc'
>> gmake[1]: *** [all-gcc] Error 2
> Thanks for pointing these things out. However, I hope you are filing
> bug reports about these issues you are raising. Problems which are
> only reported to the mailing list will be reliably lost and forgotten.
> If you want them to be fixed, please open bug reports. Thanks.
> Ian 		 	   		  

More information about the Gcc mailing list