1. 15 Oct, 2007 3 commits
  2. 14 Oct, 2007 1 commit
    • Sam Ravnborg's avatar
      kbuild: enable 'make CFLAGS=...' to add additional options to CC · a0f97e06
      Sam Ravnborg authored
      The variable CFLAGS is a wellknown variable and the usage by
      kbuild may result in unexpected behaviour.
      On top of that several people over time has asked for a way to
      pass in additional flags to gcc.
      This patch replace use of CFLAGS with KBUILD_CFLAGS all over the
      tree and enabling one to use:
      make CFLAGS=...
      to specify additional gcc commandline options.
      One usecase is when trying to find gcc bugs but other
      use cases has been requested too.
      Patch was tested on following architectures:
      alpha, arm, i386, x86_64, mips, sparc, sparc64, ia64, m68k
      Test was simple to do a defconfig build, apply the patch and check
      that nothing got rebuild.
      Signed-off-by: 's avatarSam Ravnborg <sam@ravnborg.org>
  3. 12 Oct, 2007 5 commits
    • Adrian Bunk's avatar
      kbuild: call export_report from the Makefile · 295ac051
      Adrian Bunk authored
      The main feature is that export_report now automatically works
      for O= builds.
      Signed-off-by: 's avatarAdrian Bunk <bunk@kernel.org>
      Signed-off-by: 's avatarSam Ravnborg <sam@ravnborg.org>
    • Milton Miller's avatar
      kbuild: call make once for all targets when O=.. is used · 0b35786d
      Milton Miller authored
      Change the invocations of make in the output directory Makefile and the
      main Makefile for separate object trees to pass all goals to one $(MAKE)
      via a new phony target "sub-make" and the existing target _all.
      When compiling with separate object directories, a separate make is called
      in the context of another directory (from the output directory the main
      Makefile is called, the Makefile is then restarted with current directory
      set to the object tree).  Before this patch, when multiple make command
      goals are specified, each target results in a separate make invocation.
      With make -j, these invocations may run in parallel, resulting in multiple
      commands running in the same directory clobbering each others results.
      I did not try to address make -j for mixed dot-config and no-dot-config
      targets.  Because the order does matter, a solution was not obvious.
      Perhaps a simple check for MAKEFLAGS having -j and refusing to run would
      be appropriate.
      Signed-off-by: 's avatarMilton Miller <miltonm@bga.com>
      Signed-off-by: 's avatarSam Ravnborg <sam@ravnborg.org>
    • Roland McGrath's avatar
      kbuild: pass -g to assembler under CONFIG_DEBUG_INFO · cf851aa7
      Roland McGrath authored
      The assembler for a while now supports -gdwarf to generate source line info
      just like the C compiler does.  Source-level assembly debugging sounds like an
      oxymoron, but it is handy to be able to see the right source file and read its
      comments rather than just the disassembly.  This patch enables -gdwarf for
      assembly files when CONFIG_DEBUG_INFO=y and the assembler supports the option.
      Signed-off-by: 's avatarRoland McGrath <roland@redhat.com>
      Cc: Sam Ravnborg <sam@ravnborg.org>
      Cc: <linux-arch@vger.kernel.org>
      Signed-off-by: 's avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: 's avatarSam Ravnborg <sam@ravnborg.org>
    • Sam Ravnborg's avatar
      kbuild: fix infinite make recursion · 4f1127e2
      Sam Ravnborg authored
      Jan Engelhardt <jengelh@computergmbh.de> reported:
      You can cause a recursion in kbuild/make with the following:
      make O=$PWD kernel/time.o
      make mrproper
      Of course no one would use O=$PWD (that's just the testcase),
      but this happened too often:
      /ws/linux/linux-2.6.23$ make O=/ws/linux/linux-2.6.23 kernel/time.o
      (Oops - should have been O=/ws/linux/obj-2.6.23!)
      Fixed by an explicit test for this case - we error
      out if output directory and source directory are the same.
      Tested-by: 's avatarJan Engelhardt <jengelh@computergmbh.de>
      Signed-off-by: 's avatarSam Ravnborg <sam@ravnborg.org>
    • Mike Frysinger's avatar
      kbuild: clean Modules.symvers in external module dirs · c34114f4
      Mike Frysinger authored
      At the moment, running `make clean` in an external module directory does a
      nice job of cleaning up with one exception: it leaves behind Modules.symvers.
      Attached patch adds this file to the clean list for external modules.
      Signed-off-by: 's avatarMike Frysinger <vapier@gentoo.org>
      Signed-off-by: 's avatarSam Ravnborg <sam@ravnborg.org>
  4. 11 Oct, 2007 4 commits
  5. 09 Oct, 2007 1 commit
  6. 02 Oct, 2007 1 commit
    • Linus Torvalds's avatar
      Linux 2.6.23-rc9 · 3146b39c
      Linus Torvalds authored
      No, I didn't want to do this, but we had more stuff go in after -rc8
      than we had in the previous -rc. Gaah.
  7. 25 Sep, 2007 1 commit
  8. 19 Sep, 2007 1 commit
  9. 11 Sep, 2007 1 commit
  10. 01 Sep, 2007 1 commit
  11. 28 Aug, 2007 1 commit
  12. 13 Aug, 2007 1 commit
  13. 04 Aug, 2007 1 commit
  14. 25 Jul, 2007 1 commit
  15. 22 Jul, 2007 1 commit
  16. 19 Jul, 2007 1 commit
    • Roland McGrath's avatar
      Use --build-id ld option · 18991197
      Roland McGrath authored
      This change passes the --build-id when linking the kernel and when linking
      modules, if ld supports it.  This is a new GNU ld option that synthesizes an
      ELF note section inside the read-only data.  The note in this section contains
      unique identifying bits called the "build ID", which are generated so as to be
      different for any two linked ELF files that aren't identical.  The build ID
      can be recovered from stripped files, memory dumps, etc.  and used to look up
      the original program built, locate debuginfo or other details or history
      associated with it.  For normal program linking, the compiler passes
      --build-id to ld by default, but the option is needed when using ld directly
      as we do.
      Signed-off-by: 's avatarRoland McGrath <roland@redhat.com>
      Cc: Andi Kleen <ak@suse.de>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: Richard Henderson <rth@twiddle.net>
      Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
      Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
      Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
      Signed-off-by: 's avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: 's avatarLinus Torvalds <torvalds@linux-foundation.org>
  17. 17 Jul, 2007 3 commits
  18. 16 Jul, 2007 1 commit
  19. 08 Jul, 2007 1 commit
  20. 01 Jul, 2007 1 commit
  21. 24 Jun, 2007 1 commit
  22. 17 Jun, 2007 1 commit
  23. 05 Jun, 2007 1 commit
  24. 26 May, 2007 1 commit
  25. 19 May, 2007 1 commit
  26. 18 May, 2007 1 commit
  27. 13 May, 2007 1 commit
  28. 02 May, 2007 2 commits
    • Sam Ravnborg's avatar
      kbuild: complain about missing system calls · c53aeca0
      Sam Ravnborg authored
      Most system calls seems to get added to i386 first. This patch
      automatically generates a warning for any new system call which is
      implemented on i386 but not the architecture currently being compiled.
      On PowerPC at the moment, for example, it results in these warnings:
      init/missing_syscalls.h:935:3: warning: #warning syscall sync_file_range not implemented
      init/missing_syscalls.h:947:3: warning: #warning syscall getcpu not implemented
      init/missing_syscalls.h:950:3: warning: #warning syscall epoll_pwait not implemented
      The file scripts/checksyscalls.sh list a number of legacy system calls
      that are ignored because they only makes sense on i386 systems.
      Other contributors to this patch are Russell King <rmk+lkml@arm.linux.org.uk>
      and Stéphane Jourdois <kwisatz@rubis.org>
      Signed-off-by: 's avatarDavid Woodhouse <dwmw2@infradead.org>
      Signed-off-by: 's avatarSam Ravnborg <sam@ravnborg.org>
    • Don Mullis's avatar
      kbuild: move tags from ARCH and include/ ahead of drivers · dd7e54ad
      Don Mullis authored
      Move tags extracted from the ARCH and include/ sub-trees ahead of
      those from device drivers, so that the former will appear first
      during searches.
      Saves user time during interactive searches for certain patterns
      that happen to find unwanted matches in driver files.
      Example in emacs:
      	 "M-x find-tag PAGE_SIZE"
      	 "M-1 M-." (repeated until definition from asm-i386/page.h appears)
      Signed-off-by: 's avatarDon Mullis <dwm@meer.net>
      Signed-off-by: 's avatarSam Ravnborg <sam@ravnborg.org>