[distcc] random make Error 5

[Paul Eipper]

Hi,

it's a mix of versions:

Ubuntu 9.04 machine, distcc package from repository:
distcc 2.18.3 i486-pc-linux-gnu (protocols 1 and 2) (default port 3632)
  built Aug  5 2008 01:26:08

CentOS 5.2 machine, distcc built from tarball:
distcc 3.0 i686-pc-linux-gnu
  (protocols 1, 2 and 3) (default port 3632)
  built Sep 27 2008 15:02:53

I didn't try updating yet. No other errors before the make one, that's
the full message.
You believe it's an incompatibility issue?

--
Paul Eipper


On Wed, Oct 7, 2009 at 6:15 PM, Fergus Henderson <fergus at google.com> wrote:
> Hi,
>
> Some basic information might be helpful:
>   - what version of distcc?
>   - what OS?
>   - any other error messages before the "make: *** [DrawContext.o] Error 5"?
>
> If it is an old version of distcc, have you tried upgrading your distcc
> client and servers with a recent version, e.g. distcc 3.1?
>
> On Wed, Oct 7, 2009 at 4:16 PM, Paul Eipper <lkraider at gmail.com> wrote:
>>
>> Hi,
>>
>> we are running distcc for cross-compilation, it works fine sometimes,
>> but apparently randomly we get an error like this:
>>
>> make: *** [DrawContext.o] Error 5
>> make: *** Waiting for unfinished jobs....
>>
>> when inspecting the DrawContext.o file, it's a gzipped file containing
>> the object code. Somehow distcc failed to unzip it or something, and
>> the build fails.
>>
>> More about our setup:
>>
>> We have /home mounted from NFS, and DISTCC_DIR is set to tmpfs (each
>> user has their own dir there). The cross-compilation toolchain is
>> mounted from NFS too. Here's the env setup:
>>
>> CCACHE_DIR=/var/cache/ccache
>> CCACHE_NOLINK=1
>> CCACHE_UMASK=002
>> CCACHE_PREFIX=distcc
>> DISTCC_HOSTS="localhost/6 dev"
>> PATH=/usr/lib/ccache:$PATH
>> CONCURRENCY_LEVEL="10"
>> DISTCC_DIR=/var/lock/distcc/$USER
>>
>> HOSTS are linked through a gigabit network.
>>
>> It seems the build works flawlessly for simple builds (maybe running
>> on localhost only? didn't check), but longer ones usually trip on the
>> error described above. Manually deleting the .o file and re-running
>> the build then works, and may or may not error out on another file
>> (seemingly at random).
>>
>> Is there a way to disable gz somehow completely? Would that solve the
>> issue?
>>
>> --
>> Paul Eipper
>> __
>> distcc mailing list            http://distcc.samba.org/
>> To unsubscribe or change options:
>> https://lists.samba.org/mailman/listinfo/distcc
>
>
>
> --
> Fergus Henderson <fergus at google.com>
>