home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.os.linux.gentoo      Stupid OS you gotta compile EVERYTHING      17,684 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 16,163 of 17,684   
   pk to jef   
   Re: reinstall from stage 3   
   25 Mar 08 23:53:50   
   
   From: pk@pk.invalid   
      
   jef wrote:   
      
   > OK, I've launched emerge --update --deep world and here is the content of   
   > /var/log/emerge.log   
   >[cut]   
   > 1206482106:  === (1 of 229) Compiling/Merging (dev-libs/nspr-4.6.8::/usr/   
   > portage/dev-libs/nspr/nspr-4.6.8.ebuild)   
      
   Well, it seems you've not updated your system for a *long* time. This is   
   most likely the source of your problems. You'll have to do some manual work   
   to sort things out.   
      
   > 1206482113:  *** terminating.   
   > ****************************************   
   >   
   > and of '/var/log/portage/dev-libs:nspr-4.6.8:20080325-215506.log'.   
   >[cut]   
   > it seems that a lot of files are missing :(   
      
   First of all, updating your system on a regular basis (eg, once every 2/3   
   days or once a week), by using "emerge --sync" and "emerge -uD world" is   
   the way to go to avoid problems like this.   
      
   That said, let's see what we can do. The following are general instructions.   
   There isn't much to do, except trying to upgrade as many packages as   
   possible skipping those that fail, in the hope that those can be installed   
   later.   
      
   The general procedure is as follows: do an "emerge -uDvNt world" and let it   
   run until some package fails. When this happens, write down the name of the   
   failing package and resume the process skipping the offending package   
   using "emerge --resume --skipfirst". When there are no more packages to   
   build, try re-emerging those that had previously failed, one by one.   
      
   Depending on your situation, there are some critical packages you may want   
   to emerge before anything else, like for instance portage, python (which   
   portage is written in), linux-headers, glibc, gcc.   
      
   As a very general advice, if emerge wants to upgrade portage, do that first   
   (emerge portage), followed by linux-headers and glibc (emerge linux-headers   
   && emerge glibc). Then go with the generic procedure described above.   
      
   However, be prepared to have some trouble during the process. You can post   
   your results here and ask for help, of course.   
      
   Regards   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca