1. 01 Oct, 2013 1 commit
  2. 26 Sep, 2013 1 commit
  3. 14 Sep, 2013 1 commit
  4. 02 Sep, 2013 1 commit
  5. 25 Aug, 2013 1 commit
  6. 18 Aug, 2013 1 commit
  7. 11 Aug, 2013 1 commit
  8. 04 Aug, 2013 1 commit
  9. 28 Jul, 2013 1 commit
  10. 21 Jul, 2013 1 commit
  11. 14 Jul, 2013 1 commit
  12. 10 Jul, 2013 1 commit
    • Linus Torvalds's avatar
      Revert "Makefile: Fix install error with make -j option" · 6d128e1e
      Linus Torvalds authored
      This reverts commit d2aae847
      
      .
      
      It is completely and utterly broken.  Module install should not build
      any files, and adding broken dependencies to "help" it build files is
      complete and utter sh*t.
      
      The kernel should not be built by root, and "make install" and "make
      module_install" (that for obvious reasons need to be run as root)
      absolutely must not build any files.  They should only ever copy the
      already-built files over.
      
      So having dependencies for the install targets is wrong, wrong, wrong.
      
      If you try to install a kernel without building it first, you *should*
      get errors. The build system shouldn't try to help root build the files.
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      6d128e1e
  13. 03 Jul, 2013 1 commit
  14. 30 Jun, 2013 1 commit
  15. 28 Jun, 2013 1 commit
  16. 24 Jun, 2013 1 commit
    • Mike Marciniszyn's avatar
      kbuild: fix error when building from src rpm · c398ff00
      Mike Marciniszyn authored
      
      
      The following issue can be reproduced with Linus' tree on
      an x86_64 server.
      
      >+ cp /home/user/rpmbuild-test/BUILDROOT/kernel-3.9.2.x86_64/boot/vmlinuz-3.9.2
      >cp: missing destination file operand after
      >/home/user/rpmbuild-test/BUILDROOT/kernel-3.9.2-1.x86_64/boot/vmlinuz-3.9.2'
      >Try `cp --help' for more information.
      >error: Bad exit status from /var/tmp/rpm-tmp.R4o0iI (%install)
      
      Here are the commands to reproduce:
      
      make defconfig
      make rpm-pkg
      
      Use the resulting src rpm to build as follows:
      
      mkdir ~/rpmbuild-test
      cd ~/rpmbuild-test
      rpmbuild --rebuild --define "_topdir `pwd`" -vv ~/rpmbuild/SRPMS/kernel-3.10.0_rc1+-1.src.rpm
      
      The issue is because the %install script uses $KBUILD_IMAGE and it hasn't
      been set since it is only available in the kbuild system and not in the
      %install script.
      
      This patch adds a Makefile target to emit the image_name that can be used
      and modifies the mkspec to use the dynamic name in %install.
      Signed-off-by: default avatarMike Marciniszyn <mike.marciniszyn@intel.com>
      Signed-off-by: default avatarMichal Marek <mmarek@suse.cz>
      c398ff00
  17. 22 Jun, 2013 1 commit
  18. 15 Jun, 2013 1 commit
  19. 08 Jun, 2013 1 commit
  20. 02 Jun, 2013 1 commit
  21. 26 May, 2013 1 commit
  22. 20 May, 2013 1 commit
  23. 11 May, 2013 1 commit
  24. 29 Apr, 2013 1 commit
    • Arnd Bergmann's avatar
      Turn off -Wmaybe-uninitialized when building with -Os · e74fc973
      Arnd Bergmann authored
      
      
      gcc-4.7 and higher add a lot of false positive warnings about
      potential uses of uninitialized warnings, but only when optimizing
      for size (-Os). This is the default when building allyesconfig,
      which turns on CONFIG_CC_OPTIMIZE_FOR_SIZE.
      
      In order to avoid getting a lot of patches that initialize such
      variables and accidentally hide real errors along the way, let's
      just turn off this warning on the respective gcc versions
      when building with size optimizations. The -Wmaybe-uninitialized
      option was introduced in the same gcc version (4.7) that is now
      causing the false positives, so there is no effect on older compilers.
      
      A side effect is that when building with CONFIG_CC_OPTIMIZE_FOR_SIZE,
      we might now see /fewer/ warnings about possibly uninitialized
      warnings than with -O2, but that is still much better than seeing
      warnings known to be bogus.
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      e74fc973
  25. 28 Apr, 2013 1 commit
  26. 21 Apr, 2013 1 commit
  27. 18 Apr, 2013 1 commit
    • Michal Marek's avatar
      rpm-pkg: Do not package the whole source directory · 6615d6c3
      Michal Marek authored
      
      
      The source tree can contain lots of uninteresting data like tag or
      cscope files, packaging which slows down make rpm needlessly. It can
      also break the build, if the tree contains an unrelated file named
      *.spec. The downside of this change is that new subdirectories have to
      be added to the KBUILD_ALLDIRS variable in the top-level Makefile. The
      upside is that the behavior is more predictable.
      Signed-off-by: default avatarMichal Marek <mmarek@suse.cz>
      6615d6c3
  28. 14 Apr, 2013 1 commit
  29. 10 Apr, 2013 1 commit
  30. 07 Apr, 2013 1 commit
  31. 31 Mar, 2013 1 commit
  32. 23 Mar, 2013 1 commit
  33. 17 Mar, 2013 1 commit
  34. 15 Mar, 2013 1 commit
  35. 14 Mar, 2013 1 commit
    • Rusty Russell's avatar
      CONFIG_SYMBOL_PREFIX: cleanup. · b92021b0
      Rusty Russell authored
      
      
      We have CONFIG_SYMBOL_PREFIX, which three archs define to the string
      "_".  But Al Viro broke this in "consolidate cond_syscall and
      SYSCALL_ALIAS declarations" (in linux-next), and he's not the first to
      do so.
      
      Using CONFIG_SYMBOL_PREFIX is awkward, since we usually just want to
      prefix it so something.  So various places define helpers which are
      defined to nothing if CONFIG_SYMBOL_PREFIX isn't set:
      
      1) include/asm-generic/unistd.h defines __SYMBOL_PREFIX.
      2) include/asm-generic/vmlinux.lds.h defines VMLINUX_SYMBOL(sym)
      3) include/linux/export.h defines MODULE_SYMBOL_PREFIX.
      4) include/linux/kernel.h defines SYMBOL_PREFIX (which differs from #7)
      5) kernel/modsign_certificate.S defines ASM_SYMBOL(sym)
      6) scripts/modpost.c defines MODULE_SYMBOL_PREFIX
      7) scripts/Makefile.lib defines SYMBOL_PREFIX on the commandline if
         CONFIG_SYMBOL_PREFIX is set, so that we have a non-string version
         for pasting.
      
      (arch/h8300/include/asm/linkage.h defines SYMBOL_NAME(), too).
      
      Let's solve this properly:
      1) No more generic prefix, just CONFIG_HAVE_UNDERSCORE_SYMBOL_PREFIX.
      2) Make linux/export.h usable from asm.
      3) Define VMLINUX_SYMBOL() and VMLINUX_SYMBOL_STR().
      4) Make everyone use them.
      Signed-off-by: default avatarRusty Russell <rusty@rustcorp.com.au>
      Reviewed-by: default avatarJames Hogan <james.hogan@imgtec.com>
      Tested-by: James Hogan <james.hogan@imgtec.com> (metag)
      b92021b0
  36. 10 Mar, 2013 1 commit
  37. 03 Mar, 2013 1 commit
  38. 22 Feb, 2013 2 commits
    • Andi Kleen's avatar
      Kbuild: Disable var tracking with CONFIG_DEBUG_INFO_REDUCED · e82c4bb8
      Andi Kleen authored
      
      
      Newer gcc enables the var-tracking pass with -g to keep track which
      registers contain which variables. This is one of the slower passes in gcc.
      
      With reduced debug info (aimed at objdump -S, but not using a full debugger)
      we don't need this fine grained tracking. But it was still enabled
      because -g was enabled. Disable it explicitely for DEBUG_INFO_REDUCED.
      
      On my 8T workstation this gives me about a 12 second gain in building
      a reasonable kernel config (2min16 vs 2min28) with DEBUG_INFO_REDUCED.
      With full DEBUG_INFO it takes 2min46
      
      The actual improvement in user time taken by the compiler is much higher
      (all CPU combined user time 15min5s vs 16m30 before)
      but the usual amdahl bottleneck on the linker prevents more speedup.
      It still saves some more energy and keeps cycles for other things.
      Signed-off-by: default avatarAndi Kleen <ak@linux.intel.com>
      Signed-off-by: default avatarMichal Marek <mmarek@suse.cz>
      e82c4bb8
    • James Hogan's avatar
      depmod: pass -P $CONFIG_SYMBOL_PREFIX · 8937e897
      James Hogan authored
      
      
      On architectures which have symbol prefixes, depmod emits lots of
      warnings like this:
      
      WARNING: $module.ko needs unknown symbol $symbol
      
      This is because depmod isn't being passed the -P <symbol_prefix>
      arguments to specify the symbol prefix to ignore. This option is
      included since the 3.13 release of module-init-tools.
      
      Update scripts/depmod.sh to take extra arguments for the symbol prefix
      (required but may be empty), and update the main Makefile to always pass
      "$(CONFIG_SYMBOL_PREFIX)" to scripts/depmod.sh.
      
      If the provided symbol prefix is non-empty, scripts/depmod.sh checks if
      depmod --version reports module-init-tools with a version number < 3.13
      otherwise it appends -P $SYMBOL_PREFIX to the depmod command line.
      Signed-off-by: default avatarJames Hogan <james.hogan@imgtec.com>
      Cc: Michal Marek <mmarek@suse.cz>
      Cc: linux-kbuild@vger.kernel.org
      Cc: Mike Frysinger <vapier@gentoo.org>
      Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
      Cc: uclinux-dist-devel@blackfin.uclinux.org
      Signed-off-by: default avatarMichal Marek <mmarek@suse.cz>
      8937e897
  39. 18 Feb, 2013 1 commit