19 Feb, 2006

2 commits

  • While the recent change to also escape # symbols when storing C-file
    compilation command lines was helpful, it should be in effect for all
    command lines, as much as the dollar escaping should be in effect for
    C-source compilation commands. Additionally, for better readability and
    maintenance, consolidating all the escaping (single quotes, dollars,
    and now sharps) was also desirable.

    Signed-Off-By: Jan Beulich
    Signed-off-by: Sam Ravnborg

    Jan Beulich
     
  • Move $(CC) support functions to Kbuild.include so they are available
    in the kbuild files.
    In addition the following was done:
    o as-option documented in Documentation/kbuild/makefiles.txt
    o Moved documentation to new section to match
    new scope of functions
    o added cc-ifversion used to conditionally select a text string
    dependent on actual $(CC) version
    o documented cc-ifversion
    o change so Kbuild.include is read before the kbuild file

    Signed-off-by: Sam Ravnborg

    Sam Ravnborg
     

07 Jan, 2006

1 commit


28 Jul, 2005

1 commit

  • kbuild failed to locate Makefile for external modules.
    This brought to my attention how the variables for directories
    have different values in different usage scenarios.

    Different kbuild usage scenarios:
    make - plain make in same directory where kernel source lives
    make O= - kbuild is told to store output files in another directory
    make M= - building an external module
    make O= M= - building an external module with kernel output seperate from src

    Value assigned to the different variables:

    |$(src) |$(obj) |$(srctree) |$(objtree)
    make |reldir to k src |as src |abs path to k src |abs path to k src
    make O= |reldir to k src |as src |abs path to k src |abs path to output dir
    make M= |abs path to src |as src |abs path to k src |abs path to k src
    make O= M= |abs path to src |as src |abs path to k src |abs path to k output

    path to kbuild file:

    make | $(srctree)/$(src), $(src)
    make O= | $(srctree)/$(src)
    make M= | $(src)
    make O= M= | $(src)

    From the table above it can be seen that the only good way to find the
    home directory of the kbuild file is to locate the one of the two variants
    that is an absolute path. If $(src) is an absolute path (starts with /)
    then use it, otherwise prefix $(src) with $(srctree).

    Signed-off-by: Sam Ravnborg

    Sam Ravnborg
     

26 Jul, 2005

2 commits

  • kbuild failed to locate Kbuild.include.
    Teach kbuild how to find Kbuild files when using make O=...

    Signed-off-by: Sam Ravnborg
    ---

    Sam Ravnborg
     
  • Kbuild.include is a placeholder for definitions originally present in
    both the top-level Makefile and scripts/Makefile.build.
    There were a slight difference in the filechk definition, so the most videly
    used version was kept and usr/Makefile was adopted for this syntax.

    Signed-off-by: Sam Ravnborg
    ---

    Sam Ravnborg
     

15 Jul, 2005

1 commit

  • From: Matthew Wilcox
    I inadvertently built a tree as root and then rebuilt it as a user. I
    got a lot of prompts ...

    mv: overwrite `drivers/char/drm/drm_auth.o', overriding mode 0644?

    Using mv -f fixes that.

    Signed-off-by: Matthew Wilcox
    Signed-off-by: Sam Ravnborg

    Sam Ravnborg
     

24 Jun, 2005

1 commit


17 Apr, 2005

1 commit

  • Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds