| 1 |
On 5/31/06, Lord Sauron <lordsauronthegreat@×××××.com> wrote: |
| 2 |
> This is - for me - an emergency. No pun intended. |
| 3 |
> |
| 4 |
> I had to get rid of all gcc versions 3.4.5 and greater to work with |
| 5 |
> gcc in Cygwin on my desktop to speed up the emerge of KDE 3.5 such |
| 6 |
> that I wouldn't finish when KDE 4.0 was released. |
| 7 |
> |
| 8 |
> I gave it some pretty explicit instructions AFTER emerging |
| 9 |
> gcc-3.4.4-r1. emerge --unmerge gcc-3.4.5 gcc-3.4.5-r1 (the only two |
| 10 |
> greater that 3.4.4 that I had installed). |
| 11 |
> |
| 12 |
> For reasons that I can't fathom, gcc, is now gone. Totally. |
| 13 |
> Completely. Not there. |
| 14 |
> |
| 15 |
> I know some of you are going to be laughing your heads off at what can |
| 16 |
> only be a gigantic error in syntaxing my command to emerge, however, I |
| 17 |
> don't find it at all funny. I can't start KDE, I can't emerge gcc to |
| 18 |
> fix the problem, I can't eix gcc to see what versions of gcc are still |
| 19 |
> there, and other things. To me it looks like Python is totally |
| 20 |
> broken. It keeps asking for libstdc++.so.6, which apparently no |
| 21 |
> longer exists. |
| 22 |
> |
| 23 |
> I'm totally and completely devoid of all ideas to fix this problem. |
| 24 |
> My best idea has been to try and distcc with my desktop a version of |
| 25 |
> gcc, however, if even emerge --search won't work, I'm willing to bet |
| 26 |
> that adding FEATURES="distcc" to my make.conf won't do much more than |
| 27 |
> make a minor footnote in the list of problems I face. |
| 28 |
> |
| 29 |
> I'm pretty much scared of having to either 1) reinstall Gentoo or 2) |
| 30 |
> go back to Kubuntu, so help here would be beyond excellent. |
| 31 |
> |
| 32 |
> I'm not sure how violate an idea this is, but I think it might (some |
| 33 |
> gigantic emphasis on the might part) be possible to take another |
| 34 |
> generic i386/i686 copy of libstdc++.so.6 and paste it into where it's |
| 35 |
> needed. I think this might fix the problem so that I can the get |
| 36 |
> emerge to work enough to distcc my way into patching up my critically |
| 37 |
> wounded system. |
| 38 |
> |
| 39 |
> Before anyone makes me confess, YES! I KILLED MY SYSTEM! However, I |
| 40 |
> have to defend my pride in saying it wasn't something dumb like |
| 41 |
> blindly following some rm -r command from some website. |
| 42 |
> |
| 43 |
> Any help here would be just great. Thanks for any help you can give in advance. |
| 44 |
> |
| 45 |
|
| 46 |
Well, the world is not lost, you still have a working machine, so, you |
| 47 |
CAN fix this as long as you can BOOT your system in any way, I'm |
| 48 |
assuming you get it running (most of it), so, there's still hope. AND |
| 49 |
you have a complete working machine (your desktop), so, calm down and |
| 50 |
think straight. |
| 51 |
|
| 52 |
My best bet would be "quickpkg gcc for libstdc++ glibc" at the |
| 53 |
Desktop, then you'll need to find and and put some libs to the right |
| 54 |
places at your broken machine, till portage start working. After you |
| 55 |
get emerge working, you can use the packages generated by quickpkg to |
| 56 |
quickly restore gcc and glibc and start fixing your GCC installation. |
| 57 |
|
| 58 |
If you can't get portage to work, you may need to extract a snapshot |
| 59 |
to $PORTDIR. If you can't, in any way, you can still extract the |
| 60 |
quickpkg's using tar... Those are guesses, but, well, worth a try?! |
| 61 |
|
| 62 |
Anyway, some guru will point you in the right direction anytime. |
| 63 |
|
| 64 |
-- |
| 65 |
Daniel da Veiga |
| 66 |
Computer Operator - RS - Brazil |
| 67 |
-----BEGIN GEEK CODE BLOCK----- |
| 68 |
Version: 3.1 |
| 69 |
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- |
| 70 |
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ |
| 71 |
------END GEEK CODE BLOCK------ |
| 72 |
-- |
| 73 |
gentoo-user@g.o mailing list |
Archives