1. 18 10月, 2007 1 次提交
    • Y
      kbuild: fix typo SRCARCH in find_sources · f8bea58b
      Yinghai Lu 提交于
      otherwise get the two copy file list in SRCARCH
      
      for cscope:
      C symbol: start_kernel
      
        File           Function            Line
      0 proto.h        <global>              11 extern void start_kernel(void );
      1 start_kernel.h <global>              10 extern asmlinkage void __init start_kernel(void );
      2 head32.c       i386_start_kernel     37 start_kernel();
      3 head32.c       i386_start_kernel     37 start_kernel();
      4 head64.c       x86_64_start_kernel   85 start_kernel();
      5 head64.c       x86_64_start_kernel   85 start_kernel();
      6 head_32.S      options              199 cmpb $0,%cl #the first CPU calls start_kernel
      7 head_32.S      options              199 cmpb $0,%cl #the first CPU calls start_kernel
      8 enlighten.c    xen_start_kernel    1145 start_kernel();
      9 enlighten.c    xen_start_kernel    1145 start_kernel();
      a lguest.c       lguest_init         1095 start_kernel();
      b main.c         start_kernel         513 asmlinkage void __init start_kernel(void )
      
      after the patch:
      C symbol: start_kernel
      
        File           Function            Line
      0 proto.h        <global>              11 extern void start_kernel(void );
      1 start_kernel.h <global>              10 extern asmlinkage void __init start_kernel(void );
      2 head32.c       i386_start_kernel     37 start_kernel();
      3 head64.c       x86_64_start_kernel   85 start_kernel();
      4 head_32.S      options              199 cmpb $0,%cl #the first CPU calls start_kernel
      5 enlighten.c    xen_start_kernel    1145 start_kernel();
      6 lguest.c       lguest_init         1095 start_kernel();
      7 main.c         start_kernel         513 asmlinkage void __init start_kernel(void )
      Signed-off-by: NYinghai Lu <yinghai.lu@sun.com>
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      f8bea58b
  2. 16 10月, 2007 3 次提交
  3. 15 10月, 2007 1 次提交
    • S
      kbuild: enable 'make CFLAGS=...' to add additional options to CC · a0f97e06
      Sam Ravnborg 提交于
      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: NSam Ravnborg <sam@ravnborg.org>
      a0f97e06
  4. 13 10月, 2007 5 次提交
    • A
      kbuild: call export_report from the Makefile · 295ac051
      Adrian Bunk 提交于
      The main feature is that export_report now automatically works
      for O= builds.
      Signed-off-by: NAdrian Bunk <bunk@kernel.org>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      295ac051
    • M
      kbuild: call make once for all targets when O=.. is used · 0b35786d
      Milton Miller 提交于
      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: NMilton Miller <miltonm@bga.com>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      0b35786d
    • R
      kbuild: pass -g to assembler under CONFIG_DEBUG_INFO · cf851aa7
      Roland McGrath 提交于
      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: NRoland McGrath <roland@redhat.com>
      Cc: Sam Ravnborg <sam@ravnborg.org>
      Cc: <linux-arch@vger.kernel.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      cf851aa7
    • S
      kbuild: fix infinite make recursion · 4f1127e2
      Sam Ravnborg 提交于
      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: NJan Engelhardt <jengelh@computergmbh.de>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      4f1127e2
    • M
      kbuild: clean Modules.symvers in external module dirs · c34114f4
      Mike Frysinger 提交于
      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: NMike Frysinger <vapier@gentoo.org>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      c34114f4
  5. 11 10月, 2007 4 次提交
  6. 10 10月, 2007 1 次提交
  7. 02 10月, 2007 1 次提交
    • L
      Linux 2.6.23-rc9 · 3146b39c
      Linus Torvalds 提交于
      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.
      3146b39c
  8. 25 9月, 2007 1 次提交
  9. 20 9月, 2007 1 次提交
  10. 11 9月, 2007 1 次提交
  11. 01 9月, 2007 1 次提交
  12. 28 8月, 2007 1 次提交
  13. 13 8月, 2007 1 次提交
  14. 04 8月, 2007 1 次提交
  15. 26 7月, 2007 1 次提交
  16. 23 7月, 2007 1 次提交
  17. 20 7月, 2007 1 次提交
    • R
      Use --build-id ld option · 18991197
      Roland McGrath 提交于
      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: NRoland 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: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      18991197
  18. 17 7月, 2007 4 次提交
  19. 09 7月, 2007 1 次提交
  20. 02 7月, 2007 1 次提交
  21. 25 6月, 2007 1 次提交
  22. 17 6月, 2007 1 次提交
  23. 05 6月, 2007 1 次提交
  24. 26 5月, 2007 1 次提交
  25. 19 5月, 2007 1 次提交
  26. 18 5月, 2007 1 次提交
  27. 13 5月, 2007 1 次提交
  28. 03 5月, 2007 1 次提交
    • S
      kbuild: complain about missing system calls · c53aeca0
      Sam Ravnborg 提交于
      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: NDavid Woodhouse <dwmw2@infradead.org>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      c53aeca0