I'm still analyzing the behavior of the rulesfile you sent me. I'm
not yet certain whether what you have showed me pilot error, a bug, or
a design flaw. This in itself means that I have to clean up some
relevant parts of the language description. I'll work on that today.
In the meantime, here is the *rigt* way to get the effect you want.
-------------------------------------------------------------------------------
prefix "CONFIG_" # Stripped at read time, prepended at save time
start main # Start with the menu named 'main'
symbols
VMLINUX 'vmlinux' text
This is the raw format that is produced by the kernel build. It is
required to use any of the various source debugging tools on the kernel
itself and is the only bootable format on some architectures. It is
generally too large to be used otherwise.
.
INSTALL_VMLINUX 'Install vmlinux for debugging' text
If you are debugging a kernel, you usually need vmlinux as well as the
bootable kernel. Unless you plan to debug the kernel, reply N.
.
INSTALL_VMLINUX_NAME 'Where to install vmlinux' text
If you are debugging a kernel, you usually need vmlinux as well as the
bootable kernel. For debugging, the recommended value is
/lib/modules/KERNELRELEASE/vmlinux. The path will be prefixed by
CONFIG_INSTALL_PREFIX.
.
menus main "dummy"
menu main
VMLINUX {INSTALL_VMLINUX {INSTALL_VMLINUX_NAME$}}
default INSTALL_VMLINUX_NAME from "/boot/vmlinux"
-------------------------------------------------------------------------------
I think that clears out your bug queue, yes?
--
<a href="http://www.tuxedo.org/~esr/";>Eric S. Raymond</a>
A nation or civilization that continues to produce soft-minded men
purchases its own spiritual death on an installment plan.
--Martin Luther King, Jr.
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel
