Got this at ~11:25 PM EST/USA 3/28/06 from an emerge --sync...
Updating Portage cache: 89%!!! Cannot resolve a virtual package name
to an ebuild.
!!! This is a bug, please report it. (virtual/libintl-0).
Also, updating the Portage cache gets --real-- slow around 50% through
somewhere short of 66% -- probably around 55% ?
A re-do of the emerge --sync gave the same message at the same place.
THEN doing:
emerge --ask --deep --verbose libstdc++-v3
yields:
fgcolor=green
These are the files that I would emerge, in order:
fgcolor=red
!!! ARCH is not set... are you missing the /etc/make.profile symlink?
!!! Is the symlink correct? Is your portage tree complete?
fgcolor=default
The symlink is there, pointing to:
/usr/portage/profiles/default-linux/x86/2004.3
which **USED** to be there, but is -not- now !!!
All **was** working fine until this.
Using eth0 -- dsl_modem (1.5Mb/256Kb).
Shuttle AN35N-ultra-400-plusMCP mobo, AMD2100XP, 1GB, 120+80+120GB,
52^3CDRW,
ATI A-I-W 9600 w/ 1280x1024 + 1600x1280, assorted USB, etc, etc, blah, blah,
blah... -- not earth-endangering, but no snoozer neither, and a Westell
dsl modem from bellsouth (my provider) J.I.C. you had some need to know to
help debuging... . . . . . . ... .
I was actually looking for libstdc++.so.6, for kbasic, which I need -Now-.
(I have a backup, not too much out of date to matter --
-- has my portage tree been taken to the Recycle Bin? (guess whom's!) )
rghays,
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Rome, Georgia, USA.
--
gentoo-user@gentoo.org mailing list