[plug] Gentoo Distcc Problem

[William Kenworthy]

Check out
"http://bugs.gentoo.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&field0-0-0=product&type0-0-0=substring&value0-0-0=distcc&field0-0-1=component&type0-0-1=substring&value0-0-1=distcc&field0-0-2=short_desc&type0-0-2=substring&value0-0-2=distcc&field0-0-3=status_whiteboard&type0-0-3=substring&value0-0-3=distcc"
there are a few that may apply.

Try "FEATURES="-sandbox" emerge whatever_pkg_is_causing_prob

Try "FEATURES="-distcc -ccache" emerge whatever_pkg_is_causing_prob

Is it all packages or just some?

A missbehaving distcc can cause some weird, seemingly unrelated problems
- make sure you are using the latest version as its a lot better than
some earlier versions at building in the proper place.

BillK



On Fri, 2004-12-24 at 00:27 +0800, Timothy White wrote:
> In short I think I have a umask problem or something similar (I am
> almost certain it is a permissions problem.)
> 
> Basically I can't get distcc to work with emerge as it can't open/unlink
> the lock/state files from distcc (This is what I think is happening.)
> Googling hasn't helped.
> 
> The error and the end of a emerge ebuild. It doesn't install the
> application as far as I can see.
> ----
> ...
> making executable: /usr/lib/libpcre.so.0.0.1
> making executable: /usr/lib/libpcreposix.so.0.0.0
>  >>> Completed installing into /var/tmp/portage/libpcre-4.5/image/
> 
> ------------------ ACCESS VIOLATION SUMMARY ----------------------
> LOG FILE = "/tmp/sandbox-dev-libs_-_libpcre-4.5-14224.log"
> 
> open_wr:   /portage/.distcc/lock/cpu_localhost_0
> open_wr:   /portage/.distcc/state/binstate_14465
> unlink:    /portage/.distcc/state/binstate_14465
> ------------------------------------------------------------------
> tim at dopey tim $
> ----
> It appears that it can't remove the state and lock files.
> BUT!!
> While it is running the lock directory is as below.
> ----
> tim at dopey lock $ vdir
> total 4
> -rw-r--r--  1 root portage 1 Dec 21 06:21 
> backoff_tcp_linmedia.white.lan_3632_0
> -rw-r--r--  1 root portage 0 Dec 21 06:21 cpu_localhost_0
> -rw-r--r--  1 root portage 0 Dec 21 06:21 cpu_tcp_linmedia.white.lan_3632_0
> ---- But when it has finished ----
> tim at dopey lock $ vdir
> total 0
> -rw-r--r--  1 root portage 0 Dec 21 06:21 cpu_localhost_0
> -rw-r--r--  1 root portage 0 Dec 21 06:21 cpu_tcp_linmedia.white.lan_3632_0
> ----
> This suggests that it can remove files, just not the ones it needs to.
> 
> Other possibly useful information [1]
> It happens with a umask of 002 and 022 (the system default.)
> 
> Tim
> 
> [1]
> tim at dopey lock $ vdir ../
> total 8
> drwsrwsr-x  2 portage portage 4096 Dec 21 06:23 lock
> drwsrwsr-x  2 portage portage 4096 Dec 21 06:23 state
> _______________________________________________
> PLUG discussion list: plug at plug.linux.org.au
> http://spark.plug.linux.org.au/cgi-bin/mailman/listinfo/plug
> Committee e-mail: committee at plug.linux.org.au
-- 
William Kenworthy <billk at iinet.net.au>
Home!