On Thu, Jan 27, 2000 at 10:18:43AM +0000, Terry Dawson wrote:
> Gerd wrote:
> > one there. For people that prefer "make menuconfig" or "make xconfig" the
> > make-kpkg tool seems to be not usable.
>
> Gerd,
> make-kpkg doesn't rely on "make config".
>
> You "make menuconfig", or "make xconfig" first, then you run
> 'make-kpkg'. There is no need to use "make config", that is just what
> "make-kpkg" uses if it finds a kernel source tree without a
> configuration file.
That's correct, but there is a catch you have to be wary of.
When you run make config|menuconfig|xconfig, the makefile creates
symlinks for the asm and system include files for the appropriate
architecture.
If you run "make-kpkg clean" after configuration, it removes those
links -- actually, it runs "make mrproper" but keeps your config file
safe (mrproper would usually remove .config too). So then
"make-kpkg kernel_image" will fail because of the missing links.
There's no dependence on the text-mode config -- I never use it,
always menuconfig.
Hamish vk3sb
--
Hamish Moffatt Mobile: +61 412 011 176 [EMAIL PROTECTED]
Rising Software Australia Pty. Ltd. http://www.risingsoftware.com/
Phone: +61 3 9894 4788 Fax: +61 3 9894 3362 USA: 1 888 667 7839
