From: Keith Owens <kaos@ocs.com.au>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: kbuild-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: kbuild 2.5 problems with netfilter linking
Date: Tue, 09 Apr 2002 22:02:25 +1000 [thread overview]
Message-ID: <17932.1018353745@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Sun, 07 Apr 2002 17:36:46 +1000." <20020407173646.40d7c0b7.rusty@rustcorp.com.au>
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.
prev parent reply other threads:[~2002-04-09 12:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-06 4:48 Keith Owens
2002-04-07 7:36 ` Rusty Russell
2002-04-09 12:02 ` Keith Owens [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17932.1018353745@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®