10 Jun, 2009

1 commit

• bdefe35d4   Remove bashisms from scripts ... Browse Code »

  The '-e' option to echo and brace expansion are not guaranteed to be supported
  by a POSIX-compliant /bin/sh (e.g. dash)

  Signed-off-by: dann frazier
  Signed-off-by: Andrew Morton
  Signed-off-by: Sam Ravnborg

  dann frazier

  2009-06-10 04:37:54 +0800  

29 Jan, 2008

1 commit

• 0484f1299   kbuild: fix buglet in gcc-version.sh ... Browse Code »

  Greg Schafer reported:
  ====
  $make mrproper
  scripts/gcc-version.sh: [[: command not found

  This is on a very old host with an ancient bash as /bin/sh. But I have
  CONFIG_SHELL set and pointing to a modern bash. Something is wrong.

  This doesn't happen with 2.6.23
  ====

  Fixed using a more common string equality test.

  Signed-off-by: Sam Ravnborg
  Cc: Greg Schafer
  Cc: Jesper Juhl

  Sam Ravnborg

  2008-01-29 06:14:36 +0800  

13 Oct, 2007

1 commit

• de47062a1   kbuild: improve scripts/gcc-version.sh output a bit when called without args ... Browse Code »

  Currently, if you call scripts/gcc-version.sh without arguments it will
  generate this output :

  $ sh scripts/gcc-version.sh
  scripts/gcc-version.sh: line 12: [: =: unary operator expected
  scripts/gcc-version.sh: line 16: -E: command not found
  scripts/gcc-version.sh: line 17: -E: command not found
  0000

  Not too pretty. I believe this is an improvement :

  $ sh scripts/gcc-version.sh
  Error: No compiler specified.
  Usage:
  scripts/gcc-version.sh

  Signed-off-by: Jesper Juhl
  Signed-off-by: Sam Ravnborg

  Jesper Juhl

  2007-10-13 03:15:30 +0800  

17 Jul, 2007

1 commit

• 0ab2a272e   kbuild: New 'cc-fullversion' macro ... Browse Code »

  Prints a six-digit string including the GCC patchlevel. Also fix
  the 'usage' comment for cc-version.

  Signed-off-by: Segher Boessenkool
  Signed-off-by: Sam Ravnborg

  Segher Boessenkool

  2007-07-17 03:15:47 +0800  

17 Apr, 2005

1 commit

• 1da177e4c   Linux-2.6.12-rc2 ... Browse Code »

  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

  2005-04-17 06:20:36 +0800