[distcc] Distributing with SPARCworks 4.2 or Forte 6.1 Solaris compiler?

[Hien D. Ngo]

distcc does fall back properly and compile locally.

'-E' preprocesses to stdout (just like gcc).  If you specify a '-o filename'
option, however, it complains about about the illegal suffix if the filename
is not 'filename.o' (even though it still sends the pre-processed output to
stdout!)

'-P' preprocesses only and writes the file to filename.i by default.  It
properly honors a '-o filename.i', so it looks like this is what we'll need
to use for distcc to work on SW/Forte.

Thanks,

Hien

----- Original Message -----
From: "Martin Pool" <mbp at samba.org>
To: "Hien D. Ngo" <hien at moses.xp.com>
Cc: <distcc at lists.samba.org>; <hien at xenocom.com>
Sent: Sunday, October 20, 2002 10:45 PM
Subject: Re: [distcc] Distributing with SPARCworks 4.2 or Forte 6.1 Solaris
compiler?


> On 18 Oct 2002, "Hien D. Ngo" <hien at moses.xp.com> wrote:
> >
> > After getting past the missing 'popt' library, I was able to compile
distcc on
> > Solaris.  I'm now trying to distribute compiles using SPARCworks 4.2 and
Forte 6.1
> > on Solaris 2.6.  Is anyone using distcc + SW4 or SW6?
> >
> > If there's a modular way of implementing support for other compilers
outside of gcc,
> > I'd be game to do the work for these (broken) compilers.
> >
> > BTW, I get the following error when trying to distribute as-is:
> >
> > distcc[26907] ERROR: cpp on solmaster failed with exit code 1
> > distcc[26907] Notice: failed to distribute to "solhelper", running
locally instead
> > cc: illegal suffix of output filename
>
> Does it correctly fall back to local execution?
>
> > If I just run the 'cc' command and use '-o somefile.ext' it complains
about the same
> > thing if you don't specify 'somefile.o':
> >
> > $  /usr/local/forte-6.1/bin/cc -g -DHAVE_CONFIG_H -I.    -E xtail.c -o
foo.foo -c
> > cc: illegal suffix of output filename
> >
> > There is a '-P' option which by default writes to 'filename.i', but you
still can't
> > specify '-o' with anything other than 'somefilename.i'
>
> What do -P and -E do?
>
> > So, the compiler really wants objects named '.o', pre-processed
> > files '.i', etc.
>
> distcc uses that convention.
>
> --
> Martin
>
> You can get more with a kind word and a gnu than you can with
> a kind word alone.
>