- Jul 22, 2010
-
- Jul 12, 2010
-
- Jul 07, 2010
-
-
Michal Marek authored
Commit 0a564b26 broke LOCALVERSION for O=... builds. Ouch. Reported-by:
Stephen Rothwell <sfr@canb.auug.org.au> Reported-and-tested-by:
Rafael J. Wysocki <rjw@sisk.pl> Reported-by:
Peter Anvin <hpa@zytor.com> Signed-off-by:
Michal Marek <mmarek@suse.cz> Signed-off-by:
Linus Torvalds <torvalds@linux-foundation.org>
-
- Jul 05, 2010
-
- Jun 30, 2010
-
-
Michal Marek authored
Variables given on the make commandline are not exported to $(shell ...) commands, so run the setlocalversion script in the make rule directly. Signed-off-by:
Michal Marek <mmarek@suse.cz>
-
- Jun 18, 2010
-
-
Michal Marek authored
Now that we run scripts/setlocalversion during every build, it makes sense to move all the localversion logic there. This cleans up the toplevel Makefile and also makes sure that the script is called only once in 'make prepare' (previously, it would be called every time due to a variable expansion in an ifneq statement). No user-visible change is intended, unless one runs the setlocalversion script directly. Reported-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com> Cc: David Rientjes <rientjes@google.com> Cc: Greg Thelen <gthelen@google.com> Cc: Nico Schottelius <nico-linuxsetlocalversion@schottelius.org> Signed-off-by:
Michal Marek <mmarek@suse.cz>
-
- Jun 15, 2010
-
-
Andy Whitcroft authored
In the commit below the version string handling was modified, adding a '+' where no other version information was supplied: commit 85a256d8 Author: David Rientjes <rientjes@google.com> Date: Wed Jan 13 13:01:05 2010 -0800 From the commit the intent was as below: - when CONFIG_LOCALVERSION_AUTO is disabled, a `+' is appended if the repository has been revised beyond a tagged commit and LOCALVERSION= was not passed to "make". However if the user supplies an empty LOCALVERSION on the command line the plus suffix is still added. This form is useful in the case where the build environment knows that the version as specified is correct and complete but does not correspond to a specific tag. This patch changes the implementation to match the documentation such that specifying LOCALVERSION= on the build line is sufficient to suppress any suffix. Signed-off-by:
Andy Whitcroft <apw@canonical.com> Acked-by:
David Rientjes <rientjes@google.com> Signed-off-by:
Michal Marek <mmarek@suse.cz>
-
- Jun 12, 2010
-
- Jun 09, 2010
-
-
Michal Marek authored
Generating the file in make modules_install was broken as well, because it didn't work in a readonly filesystem and otherwise it generated a root-owned file which is not wanted. Reported-by:
Rafael J. Wysocki <rjw@sisk.pl> Signed-off-by:
Michal Marek <mmarek@suse.cz>
-
- Jun 06, 2010
-
- May 30, 2010
-
-
Linus Torvalds authored
.. and thus endeth the merge window.
-
- May 16, 2010
-
- May 10, 2010
-
- May 06, 2010
-
-
Greg Thelen authored
I'm looking Makefile in the -mm branch (dated 2010-04-28-16-53) and seeing what looks like a bug in the checking of scm-identifier. The "ifneq ($scm-identifier)" seems to always execute "ifeq ($(LOCALVERSION,)) ...". This patch fixes the checking of scm-identifier. Signed-off-by:
Greg Thelen <gthelen@google.com> Acked-by:
David Rientjes <rientjes@google.com> Signed-off-by:
Michal Marek <mmarek@suse.cz>
-
- Apr 30, 2010
-
- Apr 19, 2010
-
- Apr 13, 2010
-
- Mar 30, 2010
-
- Mar 20, 2010
-
- Mar 10, 2010
-
-
Michal Marek authored
The previous approach didn't work if one did make modules && make modules_install Add modules.builtin as dependency of _modinst_, which is the target that actually needs the file. Reported-by:
Andrew Morton <akpm@linux-foundation.org> Signed-off-by:
Michal Marek <mmarek@suse.cz>
-
- Mar 08, 2010
-
-
Michal Marek authored
Only regenerate it if the configuration has changed. Also, do this after the modules build to fix errors with some weird Makefiles that are generated during build. Reported-by:
Eric Miao <eric.y.miao@gmail.com> Signed-off-by:
Michal Marek <mmarek@suse.cz>
- Feb 24, 2010
-
- Feb 12, 2010
-
- Feb 06, 2010
-
- Feb 05, 2010
-
-
Andi Kleen authored
Better dwarf2 unwind information is a good thing, it allows better debugging with kgdb and crash and helps systemtap. Commit 00308649 ("Build with -fno-dwarf2-cfi-asm") disabled some CFI information globally to work around a module loader bug on powerpc. But this disables the better unwind tables for all architectures, not just powerpc. Move the workaround to powerpc and also add a suitable comment that's it really a workaround. This improves dwarf2 unwind tables on x86 at least. Signed-off-by:
Andi Kleen <ak@linux.intel.com> Cc: Kyle McMartin <kyle@mcmartin.ca> Signed-off-by:
Andrew Morton <akpm@linux-foundation.org> Acked-by:
Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by:
Michal Marek <mmarek@suse.cz>
-
- Feb 02, 2010
-
-
Joe Perches authored
Signed-off-by:
Joe Perches <joe@perches.com> Acked-by:
WANG Cong <xiyou.wangcong@gmail.com> Signed-off-by:
Michal Marek <mmarek@suse.cz>
-
David Rientjes authored
The LOCALVERSION= string passed to "make" will now always be appended to the kernel version after CONFIG_LOCALVERSION, if it exists, regardless of whether CONFIG_LOCALVERSION_AUTO is set or not. This allows users to uniquely identify their kernel builds with a string. If CONFIG_LOCALVERSION_AUTO is enabled, the unique SCM tag reported by setlocalversion (or .scmversion) is appended to the kernel version, if it exists. When CONFIG_LOCALVERSION_AUTO is not enabled, a `+' is appended to the kernel version to represent that the kernel has been revised since the last release unless "make LOCALVERSION=" was used to uniquely identify the build. The end result is this: - when LOCALVERSION= is passed to "make", it is appended to the kernel version, - when CONFIG_LOCALVERSION_AUTO is enabled, a unique SCM identifier is appended if the respository has been revised beyond a tagged commit, and - when CONFIG_LOCALVERSION_AUTO is disabled, a `+' is appended if the repository has been revised beyond a tagged commit and LOCALVERSION= was not passed to "make". Examples: With CONFIG_LOCALVERSION_AUTO: "make" results in v2.6.32-rc4-00149-ga3ccf63. If there are uncommited changes to the respository, it results in v2.6.32-rc4-00149-ga3ccf63-dirty. If "make LOCALVERSION=kbuild" were used, it results in v2.6.32-rc4-kbuild-00149-ga3ccf63-dirty. Without CONFIG_LOCALVERSION_AUTO, "make" results in v2.6.32-rc4+ unless the repository is at the Linux v2.6.32-rc4 commit (in which case the version would be v2.6.32-rc4). If "make LOCALVERSION=kbuild" were used, it results in v2.6.32-rc4-kbuild. Also renames variables such as localver-auto and _localver-auto to more accurately describe what they represent: localver-extra and scm-identifier, respectively. Signed-off-by:
David Rientjes <rientjes@google.com> Signed-off-by:
Michal Marek <mmarek@suse.cz>
-
Roland McGrath authored
This adds CROSS_COMPILE as a kconfig string so you can store it in .config. Then you can use plain "make" in the configured kernel build directory to do the right cross compilation without setting the command-line or environment variable every time. With this, you can set up different build directories for different kernel configurations, whether native or cross-builds, and then use the simple: make -C /build/dir M=module-source-dir idiom to build modules for any given target kernel, indicating which one by nothing but the build directory chosen. I tried a version that defaults the string with env="CROSS_COMPILE" so that in a "make oldconfig" with CROSS_COMPILE in the environment you can just hit return to store the way you're building it. But the kconfig prompt for strings doesn't give you any way to say you want an empty string instead of the default, so I punted that. Signed-off-by:
Roland McGrath <roland@redhat.com> Cc: Sam Ravnborg <sam@ravnborg.org> Cc: Anibal Monsalve Salazar <anibal@debian.org> Cc: Steven Rostedt <rostedt@goodmis.org> Cc: Michal Marek <mmarek@suse.cz> Signed-off-by:
Andrew Morton <akpm@linux-foundation.org> Signed-off-by:
Michal Marek <mmarek@suse.cz>
-
- Jan 29, 2010
-
- Jan 21, 2010
-
- Jan 13, 2010
-
-
Michal Marek authored
Setting LC_CTYPE=C breaks localized messages in some setups. With only LC_COLLATE=C and LC_NUMERIC=C, we get almost all we need, except for not so defined character classes and tolower()/toupper(). The former is not a big issue, because we can assume that e.g. [:alpha:] will always include a-zA-Z and we only ever process ASCII input. The latter seems only affect arch/sh/tools/gen-mach-types, which we can handle separately. So after this patch the meaning of ranges like [a-z], the behavior of sort and join, etc. should be the same everywhere and at the same time gcc should be able to print localized waring and error messages. LC_NUMERIC=C might not be necessary, but setting it doesn't hurt. Reported-by:
Simon Horman <horms@verge.net.au> Reported-by:
Sergei Trofimovich <slyfox@inbox.ru> Acked-by:
H. Peter Anvin <hpa@zytor.com> Tested-by:
Simon Horman <horms@verge.net.au> Tested-by:
Masami Hiramatsu <mhiramat@redhat.com> Signed-off-by:
Michal Marek <mmarek@suse.cz>
-
- Jan 06, 2010
-
- Dec 24, 2009
-
- Dec 18, 2009
-
- Dec 17, 2009
-
-
H. Peter Anvin authored
Apparently not all versions of glibc and utilities treat an empty LC_ALL as nonexistent, causing error messages to be garbled. Instead, explicitly unexport it from the environment. Reported-and-tested-by:
Masami Hiramatsu <mhiramat@redhat.com> Signed-off-by:
H. Peter Anvin <hpa@zytor.com> LKML-Reference: <4B2AC394.4030108@redhat.com> Cc: Michal Marek <mmarek@sues.cz> Cc: Roland Dreier <rdreier@cisco.com> Cc: Sam Ravnborg <sam@ravnborg.org>
-
H. Peter Anvin authored
There are a number of common Unix constructs like character ranges in grep/sed/awk which don't work as expected with LC_COLLATE set to other than C. Similarly, set LC_CTYPE and LC_NUMERIC to C to avoid other nasty surprises. In order to make sure these actually take effect we also have to clear LC_ALL. Signed-off-by:
H. Peter Anvin <hpa@zytor.com> Acked-by:
Michal Marek <mmarek@sues.cz> Acked-by:
Masami Hiramatsu <mhiramat@redhat.com> Acked-by:
Roland Dreier <rdreier@cisco.com> Cc: Sam Ravnborg <sam@ravnborg.org> LKML-Reference: <4B2A1761.4070904@suse.cz>
-
- Dec 12, 2009
-
-
Michal Marek authored
Fix typo / thinko in commit bc081dd6. Signed-off-by:
Michal Marek <mmarek@suse.cz>
-
Michal Marek authored
To make it easier for module-init-tools and scripts like mkinitrd to distinguish builtin and missing modules, install a modules.builtin file listing all builtin modules. This is done by generating an additional config file (tristate.conf) with tristate options set to uppercase 'Y' or 'M'. If we source that config file, the builtin modules appear in obj-Y. Signed-off-by:
Michal Marek <mmarek@suse.cz>
-