On 19.01.11 at 19:40, Jeff Mahoney email@example.com wrote:
I use a separate build directory from the tree in which I expand the source tree. Some files, such as Module.supported are generated automatically and placed in the source tree.
I think it is actually correct to place this in the source tree - instead of putting it in the build tree, I have been carrying this
--- head-2011-01-10.orig/scripts/Makefile.modpost +++ head-2011-01-10/scripts/Makefile.modpost @@ -84,7 +84,8 @@ modpost = scripts/mod/modpost $(if $(cross_build),-c) \ $(if $(CONFIG_ENTERPRISE_SUPPORT), \ -N $(firstword $(wildcard $(dir $(MODVERDIR))/Module.supported \ - $(objtree)/Module.supported /dev/null))) + $(objtree)/Module.supported \ + $(srctree)/Module.supported /dev/null)))
quiet_cmd_modpost = MODPOST $(words $(filter-out vmlinux FORCE, $^)) modules cmd_modpost = $(modpost) -s
(addressing in particular the case where you want to build multiple configs/arches from a single source tree) which obviously could be folded into patches.suse/supported-flag if so desired.