http://www.gentoo.org/doc/en/distcc.xml Setting up Distcc to Work With Automake Code Listing 2.6: Setting your path # export PATH="/usr/lib/ccache/bin:/usr/lib/distcc/bin:${PATH}" You can put this in your .bashrc or equivelant file to have the PATH set every time you log in What .bashrc or equivelant (the correct spelling is equivalent) is it talking about. I don't know where I should put it, and I doubt many others that read this do ether. Thank You For Your TIME # slocate .bashrc /etc/skel/.bashrc /usr/share/sandbox/sandbox.bashrc /usr/portage/profiles/base/profile.bashrc /usr/portage/profiles/default-bsd/fbsd/6.1/profile.bashrc /usr/portage/profiles/default-bsd/fbsd/6.2/profile.bashrc /usr/portage/profiles/default-bsd/profile.bashrc /usr/portage/profiles/selinux/amd64/profile.bashrc /usr/portage/profiles/selinux/2005.1/amd64/profile.bashrc /usr/portage/profiles/default-linux/ppc/dev/ppc64/2007.0/multilib/profile.bashrc /usr/portage/profiles/default-linux/ppc/dev/ppc64/2007.0/64bit-userland/profile.bashrc /usr/portage/profiles/default-linux/ppc/dev/ppc64/2007.0/32bit-userland/profile.bashrc /usr/portage/profiles/default-linux/ppc/ppc64/2006.0/multilib/profile.bashrc /usr/portage/profiles/default-linux/ppc/ppc64/2006.0/64bit-userland/profile.bashrc /usr/portage/profiles/default-linux/ppc/ppc64/2006.1/multilib/profile.bashrc /usr/portage/profiles/default-linux/ppc/ppc64/2006.1/64bit-userland/profile.bashrc /usr/portage/profiles/default-linux/ppc/ppc64/2006.1/64bit-userland-gcc4/profile.bashrc /usr/portage/profiles/default-linux/ppc/ppc64/2006.1/32bit-userland/profile.bashrc /usr/portage/profiles/default-linux/ppc/2005.1/ppc64/multilib/profile.bashrc /usr/portage/profiles/default-linux/ppc/2005.1/ppc64/64bit-userland/profile.bashrc /usr/portage/profiles/default-linux/x86/dev/2007.0/server/profile.bashrc /usr/portage/profiles/default-linux/x86/2006.1/server/profile.bashrc /usr/portage/profiles/default-linux/mips/mips64/multilib/profile.bashrc /usr/portage/profiles/default-linux/amd64/profile.bashrc /usr/portage/profiles/default-linux/amd64/2005.0/profile.bashrc /usr/portage/profiles/default-linux/amd64/2005.1/profile.bashrc /usr/portage/profiles/default-linux/amd64/2006.0/no-symlinks/profile.bashrc /usr/portage/profiles/default-linux/amd64/2006.0/32bit-userland/profile.bashrc /usr/portage/profiles/default-linux/ppc64/dev/multilib/profile.bashrc /usr/portage/profiles/default-linux/ppc64/dev/2005.1/no-multilib/profile.bashrc /usr/portage/profiles/hardened/amd64/profile.bashrc /usr/portage/profiles/uclibc/profile.bashrc /usr/portage/profiles/default-darwin/macos/10.4/profile.bashrc /null/.bashrc
*** Bug 159021 has been marked as a duplicate of this bug. ***
*** Bug 159020 has been marked as a duplicate of this bug. ***
(In reply to comment #0) > What .bashrc or equivelant (the correct spelling is equivalent) is it talking > about. I don't know where I should put it, and I doubt many others that read > this do ether. Uhh...you need to read "man bash". ;) This is an advanced guide, and you should know at least the basics of working with the shell, and hopefully even a bit of scripting, to be able to understand this. We can't exactly start from scratch in every single guide to explain that a .bashrc is where various configs and variables are sourced for an individual user...it's found in /home/username. I added the full path to it (~/) just to make it more clear, and fixed the typo. Thanks for reporting, fixed in CVS.
(In reply to comment #3) > (In reply to comment #0) > > What .bashrc or equivelant (the correct spelling is equivalent) is it talking > > about. I don't know where I should put it, and I doubt many others that read > > this do ether. > > Uhh...you need to read "man bash". ;) > > This is an advanced guide, and you should know at least the basics of working > with the shell, and hopefully even a bit of scripting, to be able to understand > this. We can't exactly start from scratch in every single guide to explain that > a .bashrc is where various configs and variables are sourced for an individual > user...it's found in /home/username. I added the full path to it (~/) just to > make it more clear, and fixed the typo. > > Thanks for reporting, fixed in CVS. > Since I will be running emerge as root shouldn't it be in /root. This it the main thing that was unclear to me. I will read the bash manual. Thanks for the advice.
typo running make as root
(In reply to comment #5) > typo running make as root > That's not a typo. Nor does it say to run as root, though it is implied, seeing as you have to setup PATH as root so the whole thing works. make -jN is just like the make you would type when, say, compiling a kernel -- you need to be root.
sorry i ment i made a typo in Comment #4. I am going to make a post in the forum. I still have to run # export PATH="/usr/lib/ccache/bin:/usr/lib/distcc/bin:${PATH}" each time i login before distcc will work with make -jN. Even thought i put it in my ~/.bashrc file. I have been reading the bash manual. It hasn't helped me with the ~/.bashrc file, but i have learned a lot. Thank You For Your Time Sorry to have bothered you and confused you with my stupid typo post.
Putting "export PATH="/usr/lib/ccache/bin:/usr/lib/distcc/bin:${PATH}" in ~/.bashrc never did work ( in the stable or unstable bash versions ), but with bash-3.2_p9-r1 putting it in /etc/bash/bashrc does work (it still is KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc-macos ~ppc64 ~s390 ~sh ~sparc ~sparc-fbsd ~x86 ~x86-fbsd"). Putting it in ~/.bash_profile in the stable release of bash did work. bash-3.2_p9-r1 cat /etc/bash/bashrc # /etc/bash/bashrc # # This file is sourced by all *interactive* bash shells on startup, # including some apparently interactive shells such as scp and rcp # that can't tolerate any output. So make sure this doesn't display # anything or bad things will happen !
