Hi, On Fri, 23 Sep 2005 00:23:05 +0100 "Rupert Young (Restart)" <[EMAIL PROTECTED]> wrote:
> > I was having a problem updating my system, but I think I have a more > fundamental problem. I'm not sure what my architecture is! > > Sorry for the dumb question. > > uname -a, gives the following > > Linux fluffy 2.6.7-gentoo-r14 #1 SMP Wed Aug 18 09:57:23 UTC 2004 > x86_64 AMD Opteron(tm) Processor 250 AuthenticAMD GNU/Linux > > Does this mean my arch is x86 or amd? > Check "man uname", specially -i, -m, -o, -p flags (-a does it too). IMO it's AMD-64-bits, still no experience with such arch. > For those who have managed to get this far without collapsing in fits > of hysterics a bit of history, > > * Someone installed gentoo about a year ago for me. > * Last week I wanted to add some apps and as I was finding probs > decided to do an upadate. > * I think I did emerge sync first. > * then tried emerge -uDpv world > * somewhere I had a problem that make.profile was not linked > * I did a symbolic link to the amd64 2005.1 dir > * then had various problems, such as > !!! ERROR: sys-devel/gcc-3.4.4-r1 failed, > when doing emerge -uv system > > I have now link make.profile to > /usr/portage/profiles/default-linux/x86/2005.1 > > Was this right? > > I then did emerge --sync and etc-update on 61 config files. > > Now getting the error below on emerge -upv system. > > Am I barking up the right tadpole? > > !!! All ebuilds that could satisfy "sys-libs/libstdc++-v3" have been > masked. !!! One of the following masked packages is required to > complete your request: > - sys-libs/libstdc++-v3-3.3.3-r1 (masked by: ~x86 keyword) > - sys-libs/libstdc++-v3-3.3.4 (masked by: ~x86 keyword) > - sys-libs/libstdc++-v3-3.3.6 (masked by: ~x86 keyword) > > For more information, see MASKED PACKAGES section in the emerge man > page or section 2.2 "Software Availability" in the Gentoo Handbook. > > > !!! Problem with ebuild sys-devel/gcc-3.4.1-r1 > !!! Possibly a DEPEND/*DEPEND problem. > > !!! Depgraph creation failed. > > Regards, > > Rupert > > > -----Original Message----- > > From: Michael Kintzios [mailto:[EMAIL PROTECTED] > > Sent: 22 September 2005 14:19 > > To: gentoo-user@lists.gentoo.org > > Subject: RE: [gentoo-user] System update problems > > > > > > > > > -----Original Message----- > > > From: Rupert Young (Restart) > > > [mailto:[EMAIL PROTECTED] > > > Sent: 22 September 2005 12:25 > > > To: gentoo-user@lists.gentoo.org > > > Subject: RE: [gentoo-user] System update problems > > > > > > > > > Thanks. Unless anyone else has any suggestions I will try it. > > > > > > Can anyone else confirm this is the way to go before I try? > > > > It depends how patient you are. The suggested fix will bring your > > machine up to an "as new" condition. On the other hand, it might > > unnecessarily rebuilt packages that may not be broken or need > > updating (yet) and will take years to complete (well, it depends on > > how fast your machine is :-) That said I would think that after a > > whole year there wouldn't be much left in portage, which has not a > > new ebuild? > > > > As an alternative, if your machine is not totally hosed you could > > start from the bottom up rebuilding the core packages and after a > > fresh --sync, update the whole world. Try re-emerging the gentoo > > toolkit: gcc-config glibc binutils libstdc++. Run # etc-update and > > # env-update && source /etc/profile as required and rebuild > > portage; do another --sync; and then emerge -upDv world to see what > > comes up in need for an update. > > > > However, if basic compilers, etc. are broken you will not be able to > > re-emerge the toolkit and the solution suggested by Dave remains the > > best option. > > -- > > Regards, > > Mick > > > > -- > > gentoo-user@gentoo.org mailing list > > > HTH. Rumen
pgpo3Qg7p4jcs.pgp
Description: PGP signature
