| 1 |
On Wed, 2003-02-19 at 19:56, Terje Kvernes wrote: |
| 2 |
> MAL <mal@×××××××.com> writes: |
| 3 |
> |
| 4 |
> [ ... ] |
| 5 |
> |
| 6 |
> > So I look for the elusive /usr/sbin/gcc-config, and lo and behold it's |
| 7 |
> > missing?! I ran it a few days ago! |
| 8 |
> > |
| 9 |
> > So, promptly onto emerge gcc-config, which appears to emerge |
| 10 |
> > successfully, but produces the following messages: |
| 11 |
> > |
| 12 |
> > * Adding compat symlinks... |
| 13 |
> > /usr/lib/portage/bin/newbin: line 13: dobin: command not found |
| 14 |
> > /usr/lib/portage/bin/prepall: line 6: prepallman: command not found |
| 15 |
> > /usr/lib/portage/bin/prepall: line 7: prepallinfo: command not found |
| 16 |
> > /usr/lib/portage/bin/prepall: line 8: prepallstrip: command not found |
| 17 |
> > >>> Completed installing into /var/tmp/portage/gcc-config-1.3.1/image/ |
| 18 |
> > |
| 19 |
> > The build continues and completes... but.. gcc-config is not on the |
| 20 |
> > system?! in either /usr/bin/gcc-config or /usr/sbin/gcc-config. |
| 21 |
> > It looks like the build hasn't written any files out. |
| 22 |
> |
| 23 |
> the same thing happens here. reverting to portage 2.0.46-whatever |
| 24 |
> fixed the problem. this also made forkbombs on my box, since even |
| 25 |
> restarting X uses the GCC preprocessor, which didn't quite do it's |
| 26 |
> thing. this is, for the record, a 1.2-based system. I'll submit to |
| 27 |
> bugzilla eventually, when it's not 4am. :-) |
| 28 |
> |
| 29 |
> and yes, I've included MAL explicitly in the To:-header. |
| 30 |
|
| 31 |
I'm willing to bet that the problem is caused by that particular |
| 32 |
ebuild's changing of the PATH. Just a thought. ;) |
| 33 |
|
| 34 |
-- |
| 35 |
--Eric Andresen |
| 36 |
ndiin@×××.edu |
| 37 |
|
| 38 |
|
| 39 |
-- |
| 40 |
gentoo-dev@g.o mailing list |
Archives