1. 01 7月, 2006 1 次提交
    • S
      kbuild: fix ia64 breakage after introducing make -rR · 5e8d780d
      Sam Ravnborg 提交于
      kbuild used $¤(*F to get filename of target without extension.
      This was used in several places all over kbuild, but introducing
      make -rR broke his for all cases where we specified full path to
      target/prerequsite. It is assumed that make -rR disables old style
      suffix-rules which is why is suddenly failed.
      
      ia64 was impacted by this change because several div* routines in
      arch/ia64/lib are build using explicit paths and then kbuild failed.
      
      Thanks to David Mosberger-Tang <David.Mosberger@acm.org> for an explanation
      what was the root-cause and for testing on ia64.
      
      This patch also fixes two uses of $(*F) in arch/um
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      5e8d780d
  2. 25 6月, 2006 5 次提交
    • S
      kbuild: trivial fixes in Makefile · 070b98bf
      Sam Ravnborg 提交于
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      070b98bf
    • M
      kbuild: adding symbols in Kconfig and defconfig to TAGS · e838db68
      Masatake YAMATO 提交于
      I'm using TAGS generated from "make TAGS" to read the kernel source code.
      
      When I met a ifdef block
      
      	  #ifdef CONFIG_FOO
      	  	 ...
      	  #endif
      
      in the soruce code I would like to know the meaning CONFIG_FOO
      to decide whether I should read inside the ifdef block
      or not. meaning CONFIG_FOO is well documented in Kconfig.
      So it is nice if I can jump to CONFIG_FOO entry in Kconfig
      from "#ifdef CONFIG_FOO" with the tag jump.
      
      Here is the patch to add symbols in Kconfig and defconfig to TAGS
      in "make TAGS" operation.
      Signed-off-by: NMasatake YAMATO <jet@gyve.org>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      e838db68
    • A
      kbuild: support for %.symtypes files · 15fde675
      Andreas Gruenbacher 提交于
      Here is a patch that adds a new -T option to genksyms for generating dumps of
      the type definition that makes up the symbol version hashes. This allows to
      trace modversion changes back to what caused them. The dump format is the
      name of the type defined, followed by its definition (which is almost C):
      
        s#list_head struct list_head { s#list_head * next , * prev ; }
      
      The s#, u#, e#, and t# prefixes stand for struct, union, enum, and typedef.
      The exported symbols do not define types, and thus do not have an x# prefix:
      
        nfs4_acl_get_whotype int nfs4_acl_get_whotype ( char * , t#u32 )
      
      The symbol type defintion of a single file can be generated with:
      
        make fs/jbd/journal.symtypes
      
      If KBUILD_SYMTYPES is defined, all the *.symtypes of all object files that
      export symbols are generated.
      
      The single *.symtypes files can be combined into a single file after a kernel
      build with a script like the following:
      
      for f in $(find -name '*.symtypes' | sort); do
          f=${f#./}
          echo "/* ${f%.symtypes}.o */"
          cat $f
          echo
      done \
      | sed -e '\:UNKNOWN:d' \
            -e 's:[,;] }:}:g' \
            -e 's:\([[({]\) :\1:g' \
            -e 's: \([])},;]\):\1:g' \
            -e 's: $::' \
            $f \
      | awk '
      /^.#/   { if (defined[$1] == $0) {
                  print $1
                  next
                }
                defined[$1] = $0
              }
              { print }
      '
      
      When the kernel ABI changes, diffing individual *.symtype files, or the
      combined files, against each other will show which symbol changes caused the
      ABI changes. This can save a tremendous amount of time.
      
      Dump the types that make up modversions
      Signed-off-by: NAndreas Gruenbacher <agruen@suse.de>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      15fde675
    • R
      kbuild: fix silentoldconfig recursion · 3041e47e
      Roman Zippel 提交于
      kconfig-fix-config-dependencies causes this:
      
      make CC=cc  KBUILD_VERBOSE=1 -C /usr/src/25 SUBDIRS=/home/akpm/NVIDIA-Linux-x86_64-1.0-8762-pkg2/usr/src/nv modules
      make -f /usr/src/devel/Makefile silentoldconfig
      make -f /usr/src/devel/Makefile silentoldconfig
      make -f /usr/src/devel/Makefile silentoldconfig
      
      The basic problem is if we compile external modules, config-targets isn't
      set which can cause recursive calls to silentoldconfig to update the
      kernel configuration.
      
      Bail out and ask the user to update manually.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      3041e47e
    • T
      kbuild: add option for stripping modules while installing them · ac031f26
      Theodore Ts'o 提交于
      Add option for stripping modules while installing them.
      
      This function adds support for stripping modules while they are being
      installed.  CONFIG_DEBUG_KERNEL (which will probably become more
      popular as developers use kdump) causes the size of the installed
      modules to grow by a factor of 9 or so.
      
      Some kernel package systems solve this problem by stripping the debug
      information from /lib/modules after running "make modules_install",
      but that may not work for people who are installing directly into
      /lib/modules --- root partitions that were sized to handle 16 megs
      worth of modules may not be quite so happy with 145 megs of modules,
      so the "make modules_install" never succeeds.
      
      This patch allows such users to request modules_install to strip the
      modules as they are installed.
      Signed-off-by: N"Theodore Ts'o" <tytso@mit.edu>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      ac031f26
  3. 18 6月, 2006 1 次提交
    • L
      Linux v2.6.17 · 427abfa2
      Linus Torvalds 提交于
      Being named "Crazed Snow-Weasel" instills a lot of confidence in this
      release, so I'm sure this will be one of the better ones.
      427abfa2
  4. 10 6月, 2006 1 次提交
    • S
      kbuild: ignore make's built-in rules & variables · 566f81ca
      Sam Ravnborg 提交于
      kbuild does explicitly specify what to do in all cases, and each
      time make's built-in rules & variables has been used it has been a bug.
      So to speed up things and to avoid the hard-to-debug error situations
      ignore the built-in definitions.
      If any part of the kernel uses the built-in definitions the build will
      just stop there and it should be trivial to fix.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      566f81ca
  5. 09 6月, 2006 6 次提交
  6. 06 6月, 2006 1 次提交
  7. 25 5月, 2006 1 次提交
  8. 12 5月, 2006 1 次提交
  9. 08 5月, 2006 1 次提交
  10. 01 5月, 2006 1 次提交
  11. 27 4月, 2006 1 次提交
  12. 19 4月, 2006 1 次提交
  13. 06 4月, 2006 2 次提交
  14. 05 4月, 2006 1 次提交
    • S
      kbuild: fix building single targets with make O=.. single-target · bc2546a6
      Sam Ravnborg 提交于
      This fixes single targets build so it now works relaiably in
      following cases:
      - build with mixed kernel source and output files (make single-target)
      - build with separate output directory (make O=.. single-target)
      - external module with mixed kernel source and output files
        (make M='pwd' single-target)
      - external module with separate kernel source and output files
        (make O=.. M='pwd' single-target)
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      bc2546a6
  15. 03 4月, 2006 1 次提交
  16. 26 3月, 2006 1 次提交
    • A
      [PATCH] x86_64: Don't define string functions to builtin · 6edfba1b
      Andi Kleen 提交于
      gcc should handle this anyways, and it causes problems when
      sprintf is turned into strcpy by gcc behind our backs and
      the C fallback version of strcpy is actually defining __builtin_strcpy
      
      Then drop -ffreestanding from the main Makefile because it isn't
      needed anymore and implies -fno-builtin, which is wrong now.
      (it was only added for x86-64, so dropping it should be safe)
      
      Noticed by Roman Zippel
      
      Cc: Roman Zippel <zippel@linux-m68k.org>
      Signed-off-by: NAndi Kleen <ak@suse.de>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      6edfba1b
  17. 24 3月, 2006 1 次提交
    • J
      [PATCH] CONFIG_UNWIND_INFO · 604bf5a2
      Jan Beulich 提交于
      As a foundation for reliable stack unwinding, this adds a config option
      (available to all architectures except IA64 and those where the module
      loader might have problems with the resulting relocations) to enable the
      generation of frame unwind information.
      Signed-off-by: NJan Beulich <jbeulich@novell.com>
      Cc: Miles Bader <uclinux-v850@lsi.nec.co.jp>
      Cc: "Luck, Tony" <tony.luck@intel.com>
      Cc: Ralf Baechle <ralf@linux-mips.org>
      Cc: Kyle McMartin <kyle@mcmartin.ca>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: Paul Mundt <lethal@linux-sh.org>,
      Cc: Andi Kleen <ak@muc.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      604bf5a2
  18. 21 3月, 2006 2 次提交
  19. 20 3月, 2006 1 次提交
  20. 13 3月, 2006 1 次提交
    • A
      Kconfig: remove the CONFIG_CC_ALIGN_* options · 8cab77a2
      Adrian Bunk 提交于
      I don't see any use case for the CONFIG_CC_ALIGN_* options:
      - they are only available if EMBEDDED
      - people using EMBEDDED will most likely also enable
        CC_OPTIMIZE_FOR_SIZE
      - the default for -Os is to disable alignment
      
      In case someone is doing performance comparisons and discovers that the
      default settings gcc chooses aren't good, the only sane thing is to discuss
      whether it makes sense to change this, not through offering options to change
      this locally.
      Signed-off-by: NAdrian Bunk <bunk@stusta.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      8cab77a2
  21. 12 3月, 2006 1 次提交
  22. 11 3月, 2006 1 次提交
  23. 09 3月, 2006 1 次提交
  24. 06 3月, 2006 1 次提交
  25. 05 3月, 2006 1 次提交
  26. 27 2月, 2006 1 次提交
  27. 23 2月, 2006 1 次提交
  28. 19 2月, 2006 2 次提交