The handbook steps for setting up genkernel are [1]:

  # emerge gentoo-sources genkernel
  # genkernel --menuconfig all  # optional
  # genkernel all

If you stay conservative (e.g. ext2/3 boot partition), there's no need
for the menuconfig step.  However, when I try and build a stage4
using:

  # cat default-stage4-i686-2013.1.spec
  …
  boot/kernel: gentoo
  boot/kernel/gentoo/sources: gentoo-sources
  # catalyst -f spec/default-stage4-i686-2013.1.spec

I get:

  /proc is still mounted; performing auto-bind-umount... Auto-unbind 
successful...
  Traceback (most recent call last):
  File "/usr/lib/catalyst/catalyst", line 214, in build_target
      mytarget.run()
  File "modules/generic_stage_target.py", line 1290, in run
      apply(getattr(self,x))
  File "modules/generic_stage_target.py", line 1420, in build_kernel
      if not os.path.exists(self.settings["boot/kernel/"+kname+"/config"]):
  KeyError: 'boot/kernel/gentoo/config'
  !!! catalyst: Error encountered during run of target stage4

What's changed?  Why do I need to seed catalyst with a config file,
when I don't need to from the handbook instructions?  Maybe this usage
is just unimplemented because nobody has needed it yet?

Thanks,
Trevor

[1]: 
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=7#doc_chap4

-- 
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to