On Sun, 7 Apr 2002 17:36:46 +1000,
Rusty Russell <rusty@rustcorp.com.au> wrote:
>On Sat, 06 Apr 2002 14:48:02 +1000
>Keith Owens <kaos@ocs.com.au> wrote:
>> * Change kbuild 2.5 to detect multi linked objects and not set
>> KBUILD_OBJECT for those objects. It follows that multi linked
>> objects cannot have module or boot parameters, so change modules.h to
>> barf on MODULE_PARM() and __setup() when KBUILD_OBJECT is not
>> defined.
>>
>> I am tending towards the second solution.
>
>You missed "#include "foo.c"" as a possible workaround. Note that it's
>a waste of disk space, not memory, since these cannot be loaded at the
>same time.
I have implemented the second solution. Multi linked objects get no
value for KBUILD_OBJECT. I had to do this anyway, depending on which
order the objects were compiled, kbuild was registering different
values for KBUILD_OBJECT. That was causing spurious rebuilds and the
command appeared to change.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Apr 15 2002 - 22:00:12 EST