Thanks to all. It started at 1 of 156. By my calulation that looks correct:
103 of 260 passed 104 failed 1 of 156 to do 103+156=259 Looks great! Thanks! Now, how will I figure out why portage wanted to build alsa-driver for -e gnome? Does that require reading the gnome ebuild? (A capability I'm not sure I have...) Thanks, Mark On Thu, 17 Feb 2005 13:16:48 -0600, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > On Thu, Feb 17, 2005 at 11:11:28AM -0800, Mark Knecht wrote: > > Hi, > > After looking into a problem with Evolution it appears that a few > > people solved the problem doing an 'emerge -e gnome' so I decided to > > give that a try. It ran for 4 hours and got to item 104 out of 260 and > > then failed because for some reason portage wasn't smart about the > > alsa-driver and 2.6 kernels: > > > > >>> emerge (104 of 260) media-sound/alsa-driver-1.0.8 to / > > >>> md5 src_uri ;-) alsa-driver-1.0.8.tar.bz2 > > * Determining the location of the kernel source code > > * Found kernel source directory: > > * /usr/src/linux > > * Found sources for kernel version: > > * 2.6.9-gentoo-r4 > > * Checking for suitable kernel configuration options > > * ALSA is already compiled into the kernel. > > * Please check to make sure these options are set correctly. > > * Once you have satisfied these options, please try merging > > * this package again. > > > > !!! ERROR: media-sound/alsa-driver-1.0.8 failed. > > !!! Function check_extra_config, Line 439, Exitcode 0 > > !!! Incorrect kernel configuration options > > !!! If you need support, post the topmost build error, NOT this status > > message. > > > > Why does portage do this? > > > > Anyway, if I have to restart this is there a way to pick up from here? > > How can I start emerge -e gnome with item #105 (whatever that might > > be) and not lose 4 hours of work? > > > > Thanks, > > Mark > > > > -- > > [email protected] mailing list > > Mark, > > Not at all. Resume the emerge, and skip the first broken package. This > can be done as follows: emerge --resume --skipfirst > > Then when it's done, go back and figure out why that package broke. > > Ciao, > > Aaron Kulbe > a.k.a. superlag on FreeNode > -- [email protected] mailing list
