[PATCH 0/2] kbuild updates

From: Sam Ravnborg (sam_at_ravnborg.org)
Date: 06/20/04

  • Next message: Sam Ravnborg: "[PATCH 1/2] kbuil: add deb-pkg target" 
    Date:	Sun, 20 Jun 2004 23:19:06 +0200
To: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>

    Hi Andrew, Linus.

    Here follows two kbuild patches.

    1) Add generic infrastructure for creating kernel packages.
       This moves make rpm support to scripts/package
       and add the deb-pkg target.
       The infrastructure were added because there is requests
       to add .tar.gz, .tar.gz2 support as well, and the functionality
       really did not belong in the top-level makefile.
       The implementation is simplified based on feedback on first
       patch, so one just have to set KBUILD_IMAGE in arch Makefiel
       to say what kernel image to include in the package.

    2) Improved support for external modules.
       It has been debated what to name the symlink in /lib/modules/`uname -r`
       and where it should point.
       Now that there is a possibility to build the kernel with a separate output
       directory, there is a need to utilise this in the install.
       From now on build will point to the output directory, and source will point
       to the kernel source.
       A small MAkefile is created in the output directory allowing external modules
       to continue to build independent of the kernel being built with separate
       output directory, or with ouput and source mixed.

       If the kernel is build with source and output mixed there is no change
       in behaviour.
       If the kernel is build with separate source and output directories,
       all external modules that has not yet picked up on using the kbuild
       infrastructure will fail...
       No effort whatsoever will be done to keep external modules working if they
       do not use the kbuild infrastructure. There is no reason not to do so.

            Sam
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Sam Ravnborg: "[PATCH 1/2] kbuil: add deb-pkg target"

    Relevant Pages

    • Re: [PATCH] markers-linker-generic
      ... filesystems with a different cache size, abnormal Linux scheduler latency ... Since we cannot limit the growth of the Linux kernel, ... Towards a complete tracing mechanism in the Linux kernel, ... Keeping track of the events also requires a centralized infrastructure: ...
      (Linux-Kernel)
    • My position on general ``RAS tool support infrastructure
      ... There is a tension here between generality of support infrastructure, ... the maintainability or the reliability of the kernel without the ... Somehow that suggestion seems to have gotten lost. ... On the kexec on panic path the philosophy is that the kernel is ...
      (Linux-Kernel)
    • Re: 2.6.22 -mm merge plans
      ... that the kernel should have a static marker infrastructure. ... Let this count as a vote to merge the markers once we have the infrastructure ... I agree that it would be very useful to have the full tracing stack ...
      (Linux-Kernel)
    • Testing CAM wrapper for ata(4) controller drivers
      ... I would like to present for testing patch, turning atacontrollers ... drivers into native SIMs of new CAM ATA infrastructure. ... new ATA_CAM kernel option, which allows switching between legacy and new ...
      (freebsd-current)
    • Re: 2.6.22 -mm merge plans
      ... that the kernel should have a static marker infrastructure. ... Let this count as a vote to merge the markers once we have the infrastructure ... _is_ needed to make the markers code useful then I agree that we should ...
      (Linux-Kernel)
    Loading