user/sven/linux.git/scripts/Makefile.modpost, branch stable/2.6.16.y

spelling: s/retreive/retrieve/

2006-01-09T23:10:13Z

Signed-off-by: Adrian Bunk

kbuild: introduce Kbuild.include

2005-07-25T20:10:36Z

Kbuild.include is a placeholder for definitions originally present in both the top-level Makefile and scripts/Makefile.build. There were a slight difference in the filechk definition, so the most videly used version was kept and usr/Makefile was adopted for this syntax. Signed-off-by: Sam Ravnborg ---

[PATCH] modules: put srcversion checksum in each modinfo section

2004-10-20T01:37:33Z

Separate the module source and header checksum into a separate modinfo field srcversion. With CONFIG_MODULE_SRCVERSION_ALL=y, put srcversion into every module, not just those with MODULE_VERSION("something"). Patch by Rusty Russell, trivial merging and testing by Matt Domsch Signed-off-by: Matt Domsch Signed-off-by: Rusty Russell Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

kbuild: fix stage 2 of module build

2004-08-30T22:34:05Z

When building allmodconfig the following error were seen: scripts/Makefile.modpost:86: target `fs/nls/nls_koi8-ru.ko' given more than once in the same rule. This happened for all modules with 'ko' inside their name. This bug were introduced when head ... were replaced by grep. Signed off by: Sam Ravnborg

kbuild: Solaris fixes in various kbuild Makfiles's

2004-08-29T11:32:19Z

Additional Makefile fixes for Solaris 2.8 On Solaris, 'head' doesn't take a -q argument. But we can use 'grep -h' instead, so do that in Makefile.mod{inst,post}. The built-in test to /bin/sh doesn't like 'if ! cmd' syntax, so when determining if we need to do modversion stuff, invert the if/else cases. The built-in test also doesn't understand -ef, so invoke a real version of test which does. Signed-off-by: Tom Rini Signed-off-by: Sam Ravnborg

kbuild: Bogus "has no CRC" in external module builds

2004-08-15T13:54:27Z

From: Pavel Roskin The recent fixes for the external module build have fixed the major breakage, but they left one annoyance unfixed. If CONFIG_MODVERSIONS is disabled, a warning is printed for every exported symbol that is has no CRC. For instance, I see this when compiling the standalone Orinoco driver on Linux 2.6.6-rc3: *** Warning: "__orinoco_down" [/usr/local/src/orinoco/spectrum_cs.ko] has no CRC! *** Warning: "hermes_struct_init" [/usr/local/src/orinoco/spectrum_cs.ko] has no CRC! *** Warning: "free_orinocodev" [/usr/local/src/orinoco/spectrum_cs.ko] has no CRC! [further warnings skipped] I have found that the "-i" option for modpost is used for external builds, whereas the internal modules use "-o". The "-i" option causes read_dump() in modpost.c to be called. This function sets "modversions" variable under some conditions that I don't understand. The comment before the modversions declarations says: "Are we using CONFIG_MODVERSIONS?" Apparently modpost fails to answer this question. I think it's better to use an explicit option rather than a kludge. The attached patch adds a new option "-m" that is specified if and only if CONFIG_MODVERSIONS is enabled. The patch has been successfully tested both with and without CONFIG_MODVERSIONS. Signed-off-by: Sam Ravnborg

kbuild: Move modpost files to a new subdir scripts/mod

2004-07-23T02:59:36Z

Move modpost and support files to scripts/mod. Directory named mod by Sam. From: Brian Gerst Signed-off-by: Sam Ravnborg

[PATCH] kbuild: sort modules for modpost and modinst

2004-07-11T02:29:59Z

Process modules in sorted order during modpost and modules install. Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

[PATCH] kbuild: Improved external module support

2004-04-26T16:16:34Z

From: Sam Ravnborg The external module support recently introduced caused a number of problems: - To build an external module the Module.symvers file was needed - To create the Module.symvers file a module was required - If Module.symvers was missing kbuild boiled out with an error - If vmlinux was missing also the stage 2 of module build failed (make -k) - It was not documented what was needed to actually bauild a module The following patch addresses this by adding the following functionality: - Always generate the Module.symvers file - Ignore a missing Module.symvers file - Add a new target modules_prepare, it prepares the kernel for building external modules, and is also usefull with O= - And it adds some more comments to Makefile.modpost, so others may follow it with some luck - .modpost.cmd is no longer generated This should close all reports on issues with respect to building external modules with current kernel - which has been identified as kernel problems.

[PATCH] kbuild: external module support

2004-04-12T08:05:40Z

From: Sam Ravnborg Based on initial patch from Andreas Gruenbacher there is now better support for building external modules with kbuild. The preferred syntax is now: make -C $KERNELSRC M=$PWD but the old syntax: make -C $KERNELSRC SUBDIRS=$PWD modules will remain supported. The major differences compared to before are that: 1) No attempt is made to neither check nor update any files in $KERNELSRC 2) Module versions are now supported During stage 2 of kernel compilation where the modules are built, a new file Module.symvers is created. This file contains the version for all symbols exported by the kernel and any module compiled within the kernel tree. When the external module is build the Module.symvers file is being read and symbol versions are used from that file. The purpose of avoiding any updates in the kernel src is that usually in a distribution the kernel src will be read-only, and there is no need to try to update it. And when building an external module the focus is on the module, not the kernel. I expect the distributions will start using something like this: kernel src - with no generated files. Not even .config: /usr/src/linux- Output from build: /lib/modules/linux-/build where build is a real directory with relevant output files and the appropriate .config. I have some Documentation in the pipe-line, but wants to see how this approach is received before completing it. This patch is made on top of the previously posted patch to divide make clean in three steps. And you may need to edit the following line in the patch to make it apply: %docs: scripts_basic FORCE to %docs: scripts FORCE