[distcc] distcc won't output assembly to stdout; ccache loses also
Alexandre Oliva
aoliva at redhat.com
Fri Sep 27 14:40:01 GMT 2002
On Sep 27, 2002, Martin Pool <mbp at samba.org> wrote:
>> Unfortunately, it's not easy to tell when the compiler output is
>> supposed to go to stdout and when it should go to a file.
> Why? Can't we just treat it as normal up until we open the file, and
> then point "-" at stdout?
*If* you know that's what the real compiler would do. You don't, in
general. Consider other compilers than gcc, or some broken version
of gcc that doesn't handle `-o -' properly. You'd get different
results depending on whether you compiled locally or remotely, if
your interpretation of `-o -' happened to differ from that of the
actual compiler. Better just leave it alone, I think.
And then, gcc may well be a link to ccache or distcc, and then you get
odd interactions. This puzzled me a bit until I realized I had a link
to ccache named /usr/local/bin/gcc that distcc was running instead of
/usr/bin/gcc, that produced different results than /usr/bin/gcc3
> Thanks, I applied that and added a ScanArgs test sub-case.
Thank you!
> If tridge doesn't fix it (famous slacker that he is :-)
:-)
> then I will try later.
Thanks,
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
More information about the distcc
mailing list