Summary: | Distcc monitors sometimes do not work | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Aniruddha Shankar <k> |
Component: | Current packages | Assignee: | Lisa Seelye (RETIRED) <lisa> |
Status: | RESOLVED REMIND | ||
Severity: | normal | CC: | deathwing00, rockoo |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Aniruddha Shankar
2004-05-20 22:19:05 UTC
I confirm this bug. distccmon-text does not seem to work either. I can confirm this. I'll have to dig a little to figure out what's going on... I propose making of DISTCC_DIR an environment variable. Patching distcc* to look in /etc/make.conf strikes me as a bad idea... Why not abuse /etc/profile.{bashrc,env}... portage specifically source's /etc/profile.env in ebuild.sh, and does the DISTCC_DIR existance checks there. i'm against this one, because I don't want distcc dirs mixing between portage and my regular work. a much simpler fix, just provide a bunch of shell scripts (one that I use): portage-distccmon-text #!/bin/sh source /etc/make.conf export DISTCC_DIR="$DISTCC_DIR" distccmon-text "$@" Robin, I'll see about putting this in around 2.19 or so. |