Testing using normal handbook gentoo-nofb nox md5sum stage3-i686-2006.1.tar.bz2 93913d58a0fb3d1c501349c3ae96c266 stage3-i686-2006.1.tar.bz2 md5sum portage-20060721.tar.bz2 89f13898ff2db449c43b80ee3323f4f2 portage-20060721.tar.bz2 emerge --sync then emerge gentoo-sources then emerge genkernel All OK do genkernel all errors follow - * udev: >> Compiling... COMMAND: make j1 EXTRAS="extras/scsi_id extras/volume_id extras/ata_id extras/r un_directory extras/usb_id extras/floppy extras/cdrom_id extras/firmware" USE_KL IBC=true KLCC=/var/tmp/genkernel/2042.7123.23447.14784/klibc-build/bin/klcc USE_ LOG=false DEBUG=false udevdir=/dev all * Gentoo Linux Genkernel; Version 3.3.11dESC[0m * Running with options: all * ERROR: Failed to compile the "EXTRAS="extras/scsi_id extras/volume_id extras/a ta_id extras/run_directory extras/usb_id extras/floppy extras/cdrom_id extras/fi rmware" USE_KLIBC=true KLCC=/var/tmp/genkernel/2042.7123.23447.14784/klibc-build /bin/klcc USE_LOG=false DEBUG=false udevdir=/dev all" target... * -- Grepping log... -- * -- End log... -- * Please consult /var/log/genkernel.log for more information and any * errors that were reported above. * Report any genkernel bugs to bugs.gentoo.org and * assign your bug to genkernel@gentoo.org. Please include * as much information as you can in your bug report; attaching * /var/log/genkernel.log so that your issue can be dealt with effectively. * * Please do *not* report compilation failures as genkernel bugs! * compiled OK last week with earlier release testing.
*** Bug 141837 has been marked as a duplicate of this bug. ***
*** Bug 141836 has been marked as a duplicate of this bug. ***
*** Bug 141835 has been marked as a duplicate of this bug. ***
One thing that you need to realize is that the genkernel version you're getting when you do that is not the same one that we're using on the CD. We're using a pre-release version on the CD. For you to be able to compare apples to apples, you'll need to unmask genkernel 3.4.0_pre* after you sync. If you use the on-disk snapshot (or the snapshot in the download directory) then it will work. This is also the case with several other packages, most notably, is glibc/gcc. We are using things that are not stable in the current tree. Please avoid using a snapshot from the actual tree durign testing. Thanks...
*** Bug 142075 has been marked as a duplicate of this bug. ***
Thank you Chris. So during testing I use the snapshot provided on the poseidon server and do not do emerge --sync or I unmask the unstable release of the genkernel and other packages. I will do the snapshot provided, but what would I do to unmask a pre release package, if needed. Is a reference available? Please close this bug. Thanks, Steve
The section part of the Handbook "Using Portage" gives you instructions. Also, this shouldn't be a problem after the next couple days, since we made a genkernel 3.4.0 release and have unmasked it. We'll be marking it stable shortly. There's still the issue of glibc/gcc, so you'll want to stick with the snapshot for now.
