Re: [kbuild-devel] kbuild-2.5 and the apha
On Tue, Dec 11, 2001 at 06:48:14PM -0500, Ghozlane Toumi wrote: now the thing is that i'd like to add those new tagets to the configuration tools and config help . With the config.install-2.5 everything should be ok, but i'm not sure the non-alpha guys will be happy to see in the help 3-4 build targets with no meaning for them ... There's already lots of help entries for non-global options. Is there a way we could split the help entries into arch specific entries ? like using config variables CONFIG_INSTALL_$ARCH_VMLINUX or something ? This sounds sort-of like a good idea. On powermac and chrp, building a 'vmlinux' is currently a good idea for the final target, for example. That way each arch would only see it's build targets .. is it doable ? I take it by this you modified the help msg for the default target that alpha ends up with? -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
Re: [kbuild-devel] kbuild-2.5 and the apha
On Tuesday 11 December 2001 19:26, Ghozlane Toumi wrote: On Tuesday 11 December 2001 18:54, you wrote: There's already lots of help entries for non-global options. mmmh... actually affter a quick check, i now understand we were not talking about the same things ... I was talking about the new CONFIG_INSTALL_* configuration options introduced by kbuild-2.5, and more specificaly of the options used to choose the build targets . as CML1 uses the first entry to get the help, we have to put in the help all the targets on all the arches, ouch ... hopefully this help limitation will go away with CML2. ghoz ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
Re: [kbuild-devel] kbuild-2.5 and the apha
On Tue, Dec 11, 2001 at 09:38:58PM -0500, Ghozlane Toumi wrote: I was talking about the new CONFIG_INSTALL_* configuration options introduced by kbuild-2.5, and more specificaly of the options used to choose the build targets . as CML1 uses the first entry to get the help, we have to put in the help all the targets on all the arches, ouch ... hopefully this help limitation will go away with CML2. Yes, but there will still be lots of options that aren't global :) The BZIMAGE help text for example will be x86 only. We might want to allow for (or default to) going from CONFIG_INSTALL_ARCH_TARGET to CONFIG_INSTALL_TARGET, since not all targets mean the same thing all of the time. Or we make sure the descriptions are generic enough to fit (s/lilo/bootloader/, et al). -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
Re: [kbuild-devel] kbuild-2.5 and the apha
On Tue, 11 Dec 2001 18:48:14 -0500, Ghozlane Toumi [EMAIL PROTECTED] wrote: good news, I'm able to compile and boot a kernel built with kbuild-2.5 on my alpha ... That is good news. Is there a way we could split the help entries into arch specific entries ? like using config variables CONFIG_INSTALL_$ARCH_VMLINUX or something ? AFAICT, not in CML1. The CML1 help text is under the first entry on the choice list. In CML2 each choice entry has its own help text. ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
Re: [kbuild-devel] kbuild-2.5 and the apha
On Tue, 11 Dec 2001 19:33:25 -0500, Eric S. Raymond [EMAIL PROTECTED] wrote: Keith Owens [EMAIL PROTECTED]: Is there a way we could split the help entries into arch specific entries ? like using config variables CONFIG_INSTALL_$ARCH_VMLINUX or something ? AFAICT, not in CML1. The CML1 help text is under the first entry on the choice list. In CML2 each choice entry has its own help text. Not quite yet. CML2 still uses the CML1 convention. That will change after cutover. It already works for me using cml2 1.9.6. The help text for the menu item is one entry, the individual choices have separate text. 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. Note that the `vmlinux' format is produced by ALL compilations, either as the target step, or as an intermediate step in the production of one of the other formats. . VMLINUZ 'vmlinuz' text vmlinux after being stripped to remove debugging information then compressed using gzip. This is still the same basic format as vmlinux, just smaller. . . symbols kernel_format_x86 'The format used for the installed kernel' text All kernel builds create vmlinux as an ELF object. vmlinux may not be suitable for loading, either because the bootloader cannot handle ELF or the object is too large. This option selects the format for the installed kernel. If unsure, use bzImage. . choices kernel_format_x86 # The format that the kernel is to be compiled in VMLINUX VMLINUZ BZIMAGE ZIMAGE default BZIMAGE menu installation kernel_format_x86 unless x86 suppress kernel_format_x86 ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
Re: [kbuild-devel] kbuild-2.5 and the apha
Keith Owens [EMAIL PROTECTED]: On Tue, 11 Dec 2001 19:33:25 -0500, Eric S. Raymond [EMAIL PROTECTED] wrote: Keith Owens [EMAIL PROTECTED]: Is there a way we could split the help entries into arch specific entries ? like using config variables CONFIG_INSTALL_$ARCH_VMLINUX or something ? AFAICT, not in CML1. The CML1 help text is under the first entry on the choice list. In CML2 each choice entry has its own help text. Not quite yet. CML2 still uses the CML1 convention. That will change after cutover. It already works for me using cml2 1.9.6. The help text for the menu item is one entry, the individual choices have separate text. It uses the CML1 convrntion as a fallback. -- a href=http://www.tuxedo.org/~esr/;Eric S. Raymond/a Every Communist must grasp the truth, 'Political power grows out of the barrel of a gun.' -- Mao Tse-tung, 1938, inadvertently endorsing the Second Amendment. ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
Re: [kbuild-devel] kbuild-2.5 and the apha
On Tue, 11 Dec 2001 20:41:54 -0700, Tom Rini [EMAIL PROTECTED] wrote: On Tue, Dec 11, 2001 at 09:38:58PM -0500, Ghozlane Toumi wrote: I was talking about the new CONFIG_INSTALL_* configuration options introduced by kbuild-2.5, and more specificaly of the options used to choose the build targets . as CML1 uses the first entry to get the help, we have to put in the help all the targets on all the arches, ouch ... hopefully this help limitation will go away with CML2. Yes, but there will still be lots of options that aren't global :) The BZIMAGE help text for example will be x86 only. We might want to allow for (or default to) going from CONFIG_INSTALL_ARCH_TARGET to CONFIG_INSTALL_TARGET, since not all targets mean the same thing all of the time. Or we make sure the descriptions are generic enough to fit (s/lilo/bootloader/, et al). Each arch has its own list of installable targets. VMLINUX is always allowed for every architecture because everything has to build that before converting to a bootable format. In CML1 the help text for a choice is filed under the first option on the list, i.e. VMLINUX. I tried to make that text as generic as possible but don't sweat it, in CML2 each choice gets its own help text and the problem goes away. ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
