On Monday 17 February 2003 07:49 am, brett holcomb wrote: > Check on the list - there was a long thread about it > recently along with solutions. I think the discussion was > distcc but check out the Feb 17th newsletter as it > mentions it, too. > > On Mon, 17 Feb 2003 09:45:12 -0500 > > "Eric DeLabar" <[EMAIL PROTECTED]> wrote: > >Last week, I performed an update world, and gcc 3.2.2 was > >installed. I had > >to recompile my kernel the other day to add support for > >some new hardware, > >and I would not compile because there was no gcc in my > >path. So I > >sym-linked gcc to /usr/bin, and linux compiled. Today, I > >tried updating to > >gnome 2.2. When the emerge got to gedit, it failed > >because it tried to link > >to libstdc++.la in > >/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2/lib/ when it was > >installed in > >/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.2/lib/. I created > >another sym-link for the directory and the compilation > >worked. Did I do > >something wrong when I updated world? I haven't changed > >any paths that I > >know of, and I've tried reemerging gcc, but the problem > >still isn't fixed. > >
The usual cure for "can't find gcc" is env-update and then source /etc/profile. -- Collins Richey -- [EMAIL PROTECTED] mailing list
