[distcc] distcc and qemu-arm, happy together?

Donald Webster fryfrog at gmail.com
Sun Sep 5 21:35:55 MDT 2010

Might you be able to work around this by using SSH with distcc? A host
in your list with an @ in the front uses ssh instead of the distcc
protocol (or something like that).

AIM: fryfrog
WWW: http://www.fryfrog.com

On Sun, Sep 5, 2010 at 8:17 PM,  <someone at boldandbusted.com> wrote:
> Howdy. I've been using distcc to spread my compile work across hosts for
> many years. However, now I'm branching into a different architecture for
> fun (ARM from x86). I'm using qemu-user, via some chroot and binfmt
> magic, to facilitate cross-compiling from an x86 box. When distcc is run
> under qemu-arm (with several distcc hosts configured), qemu always
> complains:
> "qemu: Unsupported syscall: 187"
> when distcc runs. Now, of course I understand that this is a real
> edge-case usage of distcc and that the real problem is within qemu, not
> distcc. However, when distcc encounters this error (something to do with
> socket support), does it actually abort remote compiles and return the
> compile to localhost? If so, is there some way I can make distcc ignore
> these errors (it does seem to be farming compile requests out, but
> perhaps at a lower rate?) Or, is there a better way to configure distcc
> such that it doesn't use this "unsupported" method of communication when
> distributing jobs?
> Thanks for distcc! :) (please reply to the list, thanks)
> Cheers,
> Jesse Adelman
> San Francisco, CA
> __
> distcc mailing list            http://distcc.samba.org/
> To unsubscribe or change options:
> https://lists.samba.org/mailman/listinfo/distcc

More information about the distcc mailing list