Lord Sauron wrote: > I fixed it. Thank God that's over... it was good to go back to the > command line a bit for me. Keeps me sharp... even despite the huge > allergies I'm experiencing right now. > > I've also added a note in my notes files to NEVER run anything like > "emerge --unmerge gcc" ever again. That was a huge mistake. Rather, > I've found through this experience gcc-config. Never knew that was > there... much to my misfortune. > > Thanks a lot for your help - Without you I'd have to reinstall, since > I'm not skilled enough to brave the world of a live-cd and chroot (I > think) into my drive to then install gcc. At least, that's what I > think my next best option was... I'm not at all familiar with chroot > though, so all I can do is speculate. I think I'll go read its man > page now in celebration of the restoration of my system. > > Also, right before I killed my system, I made something, a very very > elementary bash script (my first bash script - yay!) to toggle distcc > on and off. It's NOT terribly advanced, but it's a start... here it > is: > > localhost ~ # cat /bin/ch_distcc > #!/bin/bash > > # alternates between using make.conf and make.conf.other > # in other words, toggles between using distcc or not > > # this should be where your make.conf lives. > MAKE_DIR="/etc/"; > > mv "$MAKE_DIR"make.conf "$MAKE_DIR"buffer > mv "$MAKE_DIR"make.conf.other "$MAKE_DIR"make.conf > mv "$MAKE_DIR"buffer "$MAKE_DIR"make.conf.other > > I know it's not terribly good, it assumes that make.conf and > make.conf.other are exactly the same - except for the distcc part in > FEATURES="". But hey, it's something I can work on while chipping my > way through a excellent reference on bash I found and downloaded. > > Thanks again for your help!
I recently changed mine to this: > # FEATURES are settings that affect the functionality of portage. Most of > # these settings are for developer use, but some are available to non- > # developers as well. 'buildpkg' is an always-on setting for the > emerge > # flag of the same name. It causes binary packages to be created > of all > # packages that are merged. > FEATURES="buildpkg ccache sandbox" It sort of helps me in case I screw up. It happens sometimes, usually when we least expect it too. Glad you got it working. Dale :-) :-) -- [email protected] mailing list
