Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 34262 - Unable to use distcc for emerge system
Summary: Unable to use distcc for emerge system
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Lisa Seelye (RETIRED)
URL: http://www.gentoo.org/doc/en/distcc.x...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-11-24 08:06 UTC by Bob Bell
Modified: 2003-11-26 14:48 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bob Bell 2003-11-24 08:06:34 UTC
The distcc documentation gives directions on how distcc can be used to bootstrap
the system.  I did NOT use distcc to bootstrap, but did attempt to use distcc
after I bootstrapped, before doing an emerge system.  When I ran 'emerge
--nodeps distcc', as the documentation dictates, the configure script failed
with 'pkg-config: command not found'.

I moved on an did an emerge system without distcc, so I can no longer reproduce
this.  But it was repeatable on multiple invocations of emerge --nodeps distcc.

Reproducible: Didn't try
Steps to Reproduce:
1. bootstrap a system (starting at stage 1)
2. run emerge --nodeps distcc
Actual Results:  
Got a failure from configure reporting that on line 1 'pkg-config: command not
found'.

Expected Results:  
If the documentation is correct, distcc should have been installed.
Comment 1 SpanKY gentoo-dev 2003-11-24 08:23:02 UTC
perhaps pkgconfig needs to be added to DEPEND
Comment 2 Lisa Seelye (RETIRED) gentoo-dev 2003-11-24 08:56:10 UTC
Thanks Bob.  Looks like pkg-config stuff snuck into the Makefile and configure script without notice.

Let me ponder how to go around this.

Spanky - even if pkg-config was in the DEPEND it wouldn't help for bootstrap since pkg-config isn't present in the stage 1 tarball.
Comment 3 Jeffrey Forman (RETIRED) gentoo-dev 2003-11-24 09:03:13 UTC
bob,

one way to get around this is to just emerge pkg-config. after a 
qpkg -f /usr/bin/pkg-config i found it was in the dev-util/pkgconfig ebuild.

jforman@westernwall jforman $ qpkg -f /usr/bin/pkg-config
dev-util/pkgconfig *

try: emerge --nodeps dev-util/pkgconfig. (hopefully the distcc goddeess doesnt whine about the --nodeps ;) )
Comment 4 Bob Bell 2003-11-24 10:50:31 UTC
Thanks for the suggestion.  However, I already did an emerge system, so I bypassed this point.  I may try that if the problem still persists when I get around to installing Gentoo on my Alpha system, but I don't expect to get around to that any time soon.  I *did* try emerge pkgconfig, but obviously didn't guess the name correctly.

This bug isn't impacting me currently, but I thought it best to file it anyway.
Comment 5 Lisa Seelye (RETIRED) gentoo-dev 2003-11-24 10:59:15 UTC
Thanks for filing it all the same.

Just curious - what version of distcc was this?  2.11.2-r1?
Comment 6 Bob Bell 2003-11-25 08:56:38 UTC
I guess I'm not positive what version of distcc emerge was attempting to build, but now that I have successfully completed emerge system and emerge distcc, I have distcc 2.11.1 installed, so I'm guess that's also the version that was failing to compile earlier.
Comment 7 michael@smith-li.com 2003-11-25 12:01:31 UTC
I think the fastest fix would be to mention in the docs that it needs to be 
USE="-gtk -gnome" emerge --nodeps distcc. 

This implies that --nodeps isn't working properly. I'll search for that bug.
Comment 8 Lisa Seelye (RETIRED) gentoo-dev 2003-11-26 14:48:32 UTC
A note has been added to the updated distcc doc (waiting on docs-team to commit).