On Fri, Oct 31, 2008 at 12:38 AM, »Q« <email@example.com> wrote:
> In <loom.20081031T050157firstname.lastname@example.org>,
> James <email@example.com> wrote:
>> I've done it now, being in too big of a hurry.
>> After an emerge --sync, and the blocking packages, I
>> got in a hurry, did not think and ran:
>> emerge --unmerge sys-libs/ss sys-libs/com_err
>> sys-fs/e2fsprogs sys-libs/e2fsprogs-libs
>> So now I cannot emerge anything to fix this.
>> Here I tried (re) emerge wget:
>> wget: error while loading shared libraries: libcom_err.so.2: cannot
>> open shared object file: No such file or directory
>> Can I just copy some file over from another amd64 machine?
>> If so, which ones exactly?
>> If not, any other ideas to fix this?
> It's com_err you need to make wget work again. Using 'emerge -fpv
> com_err' should get you a list of URL(s) for the file(s) needed, then
> you can use a web browser to download them and put them in your
> distfiles/ directory. (Or if you've got them on the other machine,
> just copy them from there.)
> After you have com_err installed, use 'emerge -fuDN' to to get
> everything you need to upgrade before you unmerge the blockers again.
Well, com_err broken openssl which broke wget with "ssl" USE flag set.
I forgot to mention that part.
Disable "ssl" USE flag when you rebuild wget, then you can download
everything else you need to rebuild. When you're done, you can rebuild
wget with SSL and should probably do a revdep-rebuild to see if
anyhing else got missed. If you don't have the current wget sources in
distfiles, see if you have /any/ and try to rebuild the exact version,
that way you don't need to download manually or copy from another PC.