search

gupascal / distcc

distcc: a fast, free distributed C/C++ compiler. Automatically exported from code.google.com/p/distcc
GNU General Public License v2.0
0 stars 0 forks source link

distcc doesn't recognise the .s file extension as an input file #89

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Answering the following questions is a big help:

1. What version of distcc are you using)?
   3.1, installed from ubuntu 11.10 repository.

2. What platform are you running on? Linux Ubuntu 11.10 x86_4
   What compilare are you using? gcc 4.6.1

3. What were you trying to do?
   Compile an assembly file; gcc -c -o hello.o hello.s

4. What went wrong?
   scanning arguments: gcc -c -o hello.o hello.s
   found object/output file "hello.o"
   no visible input file
   deleted 3 temporary files
   client: 192.168.1.64:43791 OTHER exit:0 sig:0 core:0 ret:100 time:43ms

Original issue reported on code.google.com by jessica....@gmail.com on 26 Nov 2011 at 2:19

GoogleCodeExporter commented 9 years ago 
Also fails when using .S as input file extension.

Original comment by jessica....@gmail.com on 26 Nov 2011 at 2:21

GoogleCodeExporter commented 9 years ago 
Nevermind; grepping the source, I see it requires to be enabled when building 
package. Guess I'll go build from source instead...

Original comment by jessica....@gmail.com on 26 Nov 2011 at 3:23

GoogleCodeExporter commented 9 years ago 
This is working as intended; ".s" files could contain ".include" directives, 
and distcc doesn't know how to parse ".s" files for ".include" directives, so 
it doesn't try to distribute compilations that have ".s" input files, instead 
running them locally.

As you noticed, the source has #ifdef ENABLE_REMOTE_ASSEMBLE to enable 
distributed compilation for ".s" files, but this won't work if the ".s" files 
contain ".include" directives, that's why it isn't enabled by default.

Original comment by fergus.h...@gmail.com on 4 Apr 2012 at 7:11