Re: [gentoo-user] EMERGENCY - GCC GONE!

[Nick Rout]

On Wed, 31 May 2006 20:46:54 -0300
Daniel da Veiga wrote:

> On 5/31/06, Lord Sauron <lordsauronthegreat@×××××.com> wrote:
> > This is - for me - an emergency.  No pun intended.
> >
> > I had to get rid of all gcc versions 3.4.5 and greater to work with
> > gcc in Cygwin on my desktop to speed up the emerge of KDE 3.5 such
> > that I wouldn't finish when KDE 4.0 was released.
> >
> > I gave it some pretty explicit instructions AFTER emerging
> > gcc-3.4.4-r1.  emerge --unmerge gcc-3.4.5 gcc-3.4.5-r1 (the only two
> > greater that 3.4.4 that I had installed).
> >
> > For reasons that I can't fathom, gcc, is now gone.  Totally.
> > Completely.  Not there.
> >
> > I know some of you are going to be laughing your heads off at what can
> > only be a gigantic error in syntaxing my command to emerge, however, I
> > don't find it at all funny.  I can't start KDE, I can't emerge gcc to
> > fix the problem, I can't eix gcc to see what versions of gcc are still
> > there, and other things.  To me it looks like Python is totally
> > broken.  It keeps asking for libstdc++.so.6, which apparently no
> > longer exists.
> >
> > I'm totally and completely devoid of all ideas to fix this problem.
> > My best idea has been to try and distcc with my desktop a version of
> > gcc, however, if even emerge --search won't work, I'm willing to bet
> > that adding FEATURES="distcc" to my make.conf won't do much more than
> > make a minor footnote in the list of problems I face.
> >
> > I'm pretty much scared of having to either 1) reinstall Gentoo or 2)
> > go back to Kubuntu, so help here would be beyond excellent.
> >
> > I'm not sure how violate an idea this is, but I think it might (some
> > gigantic emphasis on the might part) be possible to take another
> > generic i386/i686 copy of libstdc++.so.6 and paste it into where it's
> > needed.  I think this might fix the problem so that I can the get
> > emerge to work enough to distcc my way into patching up my critically
> > wounded system.
> >
> > Before anyone makes me confess, YES!  I KILLED MY SYSTEM!  However, I
> > have to defend my pride in saying it wasn't something dumb like
> > blindly following some rm -r command from some website.
> >
> > Any help here would be just great.  Thanks for any help you can give in advance.
> >
>
> Well, the world is not lost, you still have a working machine, so, you
> CAN fix this as long as you can BOOT your system in any way, I'm
> assuming you get it running (most of it), so, there's still hope. AND
> you have a complete working machine (your desktop), so, calm down and
> think straight.
>
> My best bet would be "quickpkg gcc for libstdc++ glibc" at the
> Desktop, then you'll need to find and and put some libs to the right
> places at your broken machine, till portage start working. After you
> get emerge working, you can use the packages generated by quickpkg to
> quickly restore gcc and glibc and start fixing your GCC installation.
>
> If you can't get portage to work, you may need to extract a snapshot
> to $PORTDIR. If you can't, in any way, you can still extract the
> quickpkg's using tar... Those are guesses, but, well, worth a try?!
>
> Anyway, some guru will point you in the right direction anytime.
>

Some OK ideas have been floated here, but what if our friend doesn't
have another working gentoo machine? he needs that for quickpkg.

Suggestions for finding the packaged file on one of the dev sites is
fine, but someone needs to give the poor guy a url. Also he isn't going
to be able to install it with portage because portage isn't working
because python isn't working. Hopefull untarring it into the filesystem
will work, but any post install scripts are not going to be executed.
Therefore something like gcc-config will need to be executed, and OP
will also need to check the ebuild for other steps that may be missing
from a simple untar.


-- 
Nick Rout <nick@×××××××.nz>

-- 
gentoo-user@g.o mailing list