Jay K writes:
> Ok if I do both or the emails are just annoying?
As far as I'm concerned, it's fine to do both.
> I find that bugs are often ignored just as well (but not lost/forgotten,
> granted. :) )
Agreed on both counts.
Ian
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. :) )
Thanks,
- Jay
> To: jay.kr...@cornell.edu
> CC: gcc@gcc.gnu.org
> Subject: Re: -disable-fixincludes does
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.
-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', neede
