From: "W. Trevor King" <wking@tremily.us>
To: gentoo-catalyst@lists.gentoo.org
Subject: [gentoo-catalyst] stage4 kernel config for genkernel?
Date: Sat, 09 Feb 2013 07:15:52 -0500 [thread overview]
Message-ID: <20130209121552.GA1795@odin.tremily.us> (raw)
[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]
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 #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-02-09 12:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-09 12:15 W. Trevor King [this message]
2013-02-09 12:56 ` [gentoo-catalyst] stage4 kernel config for genkernel? Chris White
2013-02-09 13:18 ` W. Trevor King
2013-02-09 20:45 ` [gentoo-catalyst] [PATCH 0/6] Make external kernel configs optional W. Trevor King
2013-02-09 20:45 ` [gentoo-catalyst] [PATCH 1/6] generic_stage_target: Split ._build_kernel() out of .build_kernel() W. Trevor King
2013-02-09 20:45 ` [gentoo-catalyst] [PATCH 2/6] generic_stage_target: Split ._copy_kernel_config() from ._build_kernel() W. Trevor King
2013-02-09 20:45 ` [gentoo-catalyst] [PATCH 3/6] generic_stage_target.py: Dedent the bulk of ._build_kernel() W. Trevor King
2013-02-09 20:45 ` [gentoo-catalyst] [PATCH 4/6] generic_stage_target: Split ._copy_initramfs_overlay() from ._build_kernel() W. Trevor King
2013-02-09 20:45 ` [gentoo-catalyst] [PATCH 5/6] generic_stage_target: Handle unspecified boot/kernel/<kname>/config W. Trevor King
2013-02-09 20:45 ` [gentoo-catalyst] [PATCH 6/6] kmerge.sh: Make /var/tmp/${clst_kname}.config optional W. Trevor King
2013-03-01 5:57 ` [gentoo-catalyst] [PATCH] kmerge.sh: Fix line wrapping typo from 9ceebbf W. Trevor King
2013-03-01 6:06 ` Matt Turner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130209121552.GA1795@odin.tremily.us \
--to=wking@tremily.us \
--cc=gentoo-catalyst@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox