Bug 118764 – portage on Gentoo/sparc64 is unable to find virtual/libstdc++-3.3

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description Wiktor Wandachowicz 2006-01-12 04:31:54 UTC]

Hello,

Today I've thought about upgrading this old sparc64 installation (which is
almost one year old), and I've hit the follwing problem. At the end of
'emerge --sync' it displayed the message:

Cannot resolve a virtual package name to an ebuild.
!!! This is a bug, please report it. (virtual/libstdc++-3.3)

I've tried to handle this on my own (I've pasted below a copy
of the commands I've tried) but finally I've come to the conclusion
that I should file a bug instead.

So, how should I handle this gracefuly?

Regards,


======== BEGIN QUOTE ========
blade-1 / # emerge --sync
...
Number of files: 133956
Number of files transferred: 74364
Total file size: 110667009 bytes
Total transferred file size: 82727487 bytes
Literal data: 82727487 bytes
Matched data: 0 bytes
File list size: 3170828
Total bytes written: 1487461
Total bytes read: 43432725

wrote 1487461 bytes  read 43432725 bytes  37955.37 bytes/sec
total size is 110667009  speedup is 2.46

>>> Updating Portage cache:   90%!!! Cannot resolve a virtual package name to an ebuild.
!!! This is a bug, please report it. (virtual/libstdc++-3.3)

blade-1 / # emerge -av portage


Performing Global Updates: /usr/portage/profiles/updates/4Q-2002
(Could take a couple of minutes if you have a lot of binary packages.)
  .='update pass'  *='binary update'  @='/var/db move'
  s='/var/db SLOT move' S='binary SLOT move' p='update /etc/portage/package.*'
..............................................................................


Performing Global Updates: /usr/portage/profiles/updates/3Q-2004
(Could take a couple of minutes if you have a lot of binary packages.)
  .='update pass'  *='binary update'  @='/var/db move'
  s='/var/db SLOT move' S='binary SLOT move' p='update /etc/portage/package.*'
..................................................................................................................................................................................................


Performing Global Updates: /usr/portage/profiles/updates/1Q-2005
(Could take a couple of minutes if you have a lot of binary packages.)
  .='update pass'  *='binary update'  @='/var/db move'
  s='/var/db SLOT move' S='binary SLOT move' p='update /etc/portage/package.*'
..............................................................................................................................................................................................................................................................


Performing Global Updates: /usr/portage/profiles/updates/2Q-2005
(Could take a couple of minutes if you have a lot of binary packages.)
  .='update pass'  *='binary update'  @='/var/db move'
  s='/var/db SLOT move' S='binary SLOT move' p='update /etc/portage/package.*'
............................................................s...................@.@.@.......@...@................


Performing Global Updates: /usr/portage/profiles/updates/3Q-2005
(Could take a couple of minutes if you have a lot of binary packages.)
  .='update pass'  *='binary update'  @='/var/db move'
  s='/var/db SLOT move' S='binary SLOT move' p='update /etc/portage/package.*'
.................................................s..............................


Performing Global Updates: /usr/portage/profiles/updates/4Q-2005
(Could take a couple of minutes if you have a lot of binary packages.)
  .='update pass'  *='binary update'  @='/var/db move'
  s='/var/db SLOT move' S='binary SLOT move' p='update /etc/portage/package.*'
.......................@...@..........@..


Performing Global Updates: /usr/portage/profiles/updates/1Q-2006
(Could take a couple of minutes if you have a lot of binary packages.)
  .='update pass'  *='binary update'  @='/var/db move'
  s='/var/db SLOT move' S='binary SLOT move' p='update /etc/portage/package.*'
...s

These are the packages that I would merge, in order:

!!! ARCH is not set... Are you missing the /etc/make.profile symlink?
!!! Is the symlink correct? Is your portage tree complete?

blade-1 / # nano -w /etc/make.conf
blade-1 / # # make.conf looks okay
blade-1 / # ls -l /etc/make.profile
lrwxrwxrwx  1 root root 68 Apr 15  2005 /etc/make.profile -> ../usr/portage/profiles/default-linux/sparc/sparc64/2005.0/26headers
blade-1 / # cd /etc/
blade-1 etc # rm make.profile
blade-1 etc # ln -s ../usr/portage/profiles/default-linux/sparc/sparc64/2005.1 make.profile
blade-1 etc # cd
blade-1 root # emerge --metadata
skipping sync

>>> Updating Portage cache:   88%!!! Cannot resolve a virtual package name to an ebuild.
!!! This is a bug, please report it. (virtual/libstdc++-3.3)
blade-1 root # emerge -pv libstdc++

These are the packages that I would merge, in order:

Calculating dependencies   !!! Cannot resolve a virtual package name to an ebuild.
!!! This is a bug, please report it. (virtual/libstdc++-3.3)
======== END QUOTE ========

[Comment 1 Jakub Moc (RETIRED) 2006-01-12 04:37:01 UTC]

*** This bug has been marked as a duplicate of 114798 ***

[Comment 2 Wiktor Wandachowicz 2006-01-12 05:20:57 UTC]

After reading the comments for the bug #114798,
the following did the trick for me:

# emerge -avu1 --nodeps portage
# emerge -avD portage
# emerge --sync

After that I could say that I successfuly migrated from
portage-2.0.51.19 to portage-2.0.53.

A relief :-)

Thanks for a quick and accurate help!