public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Eric Andresen <ndiin1@cox.net>
To: MAL <mal@komcept.com>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] distcc
Date: 08 Feb 2003 08:59:22 -0700	[thread overview]
Message-ID: <1044719962.3696.1.camel@ndiin> (raw)
In-Reply-To: <3E44EDF9.5090208@komcept.com>

This has been fixed in the newer releases of distcc (1.0 and above) by
calling gcc-config --get-bin-path. 1.0 and 1.1 are both in ~x86 due to
the stable portage freeze, but work fine.

On Sat, 2003-02-08 at 04:46, MAL wrote:
> This is a solved problem, but I thought i'd share it with you.
> 
> On my machine at least, distccd, (which was running as nobody), wasn't 
> getting the path to gcc, (as provided by sourcing /etc/profile.env).
> 
> This was resulting in remote compiles failing with: 'gcc: command not 
> found'.
> 
> This happens because distcc isn't being run in a login shell by 
> start-stop-daemon, and so /etc/profule isn't sourced, (as it is when you 
> login).  On a side note, suing to root, didn't give me gcc either... I 
> had to add '. /etc/profile' to my root's .bashrc.
> 
> Anyway, to fix this I simply added '. /etc/profile' to 
> /etc/init.d/distccd, just before it starts distccd.
> 
> These dynamically pathed gcc's have caused me so many problems :/
> 
> MAL
> 
> 
> --
> gentoo-dev@gentoo.org mailing list
-- 
--Eric Andresen
  ndiin@asu.edu


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-02-08 16:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-08 11:46 [gentoo-dev] distcc MAL
2003-02-08 15:59 ` Eric Andresen [this message]
2003-02-09 11:21 ` Nick Jones
2003-02-09 19:11   ` MAL
2003-02-09 20:38     ` Jon Nall
2003-02-09 21:01     ` [gentoo-dev] Re: [gentoo-user] " Martin Schlemmer
2003-02-10 20:04       ` nealbirch
  -- strict thread matches above, loose matches on Subject: below --
2004-02-23  5:26 [gentoo-dev] Distcc Lisa Seelye
2002-10-12 22:58 [gentoo-dev] distcc Wout Mertens
2002-10-13  3:28 ` Evan Read

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1044719962.3696.1.camel@ndiin \
    --to=ndiin1@cox.net \
    --cc=gentoo-dev@gentoo.org \
    --cc=mal@komcept.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox