Answering the following questions is a big help:
1. What version of distcc are you using (e.g. "2.7.1")? You can run "distcc
--version" to see. If you got distcc from a distribution package rather than
building from source, please say which one.
3.2rc1
2. What platform are you running on (e.g. "Red Hat 8.0", "HP-UX 11.11")? What
compilare are you using ("gcc 3.3")? Run "uname -a" and "cc --version" to see.
Debian 6
3. What were you trying to do (e.g. "install distcc", "build Mozilla")?
make install-deb
4. What went wrong? Did you get an error message, did it hang, did it build a
program that didn't work, did it not distribute compilation to machines that
ought to get it?
No go. Fails on dpkg install.
5. If you have an example of a compiler invocation that failed, quote it, in
full e.g.:
distcc gcc -DHAVE_CONFIG_H -D_GNU_SOURCE -I./src \ "-DSYSCONFDIR=\"/etc/\"" -I./lzo -g -O2 -W -Wall -W \ -Wimplicit -Wshadow -Wpointer-arith -Wcast-align \ -Wwrite-strings -Waggregate-return -Wstrict-prototypes \ -Wmissing-prototypes -Wnested-externs -o src/clirpc.o \ -c src/clirpc.c
Default.
6. What error logging do you get? Turn on client and server error logging. On
the client, set these environment variables, and try to reproduce the problem:
=export DISTCC_VERBOSE=1 DISTCC_LOG=/tmp/distcc.log=. Start the server with
the --verbose option. If the problem is intermittent, leave logging enabled and
then pull out the lines from the log file when the problem recurs.
File not found (/tmp/distcc-install-deb-XXXXX)
7. If you got an error message on stderr, quote that error exactly. Find the
lines in the log files pertaining to the compile, and include all of them in
your report, by looking at the process ID in square brackets. If you can't work
that out, quote the last few hundred lines leading up to the failure.
Sorry... Not worth it. Simple error to fix. Swap rpm with deb and vis versa.
Also Deb 6 systems do not have alien installed by default. Perhaps mention as
prerequisites.
Original issue reported on code.google.com by p...@bencom.co.nz on 11 Dec 2012 at 2:17
Original issue reported on code.google.com by
p...@bencom.co.nz
on 11 Dec 2012 at 2:17