From: Sam Ravnborg <sam@ravnborg.org>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Module compilation
Date: Thu, 21 Oct 2004 22:15:45 +0200 [thread overview]
Message-ID: <20041021201545.GA16474@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0410201034590.12062@chaos.analogic.com>
On Wed, Oct 20, 2004 at 10:36:00AM -0400, Richard B. Johnson wrote>
> ...but it's not CFLAGS that needs to be modified, it's
> a named variable that doesn't exist yet, perhaps "USERDEF",
> or "DEFINES".
Reading the above I cannot what amkes you say that EXTRA_CFLAGS
or CFLAGS_module.o cannot be used?
Is it the name you do not like or is it some fnctionality
you are missing?
>I see that the normal "defines" is a constant
> called "CHECKFLAGS", so this isn't appropriate for user
> modification.
CHECKFLAGS is only used when you use "make C=1" - to pass options
to sparse.
Sam
next prev parent reply other threads:[~2004-10-21 18:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 14:36 Richard B. Johnson
2004-10-20 14:49 ` David Woodhouse
2004-10-20 15:01 ` Richard B. Johnson
2004-10-20 14:59 ` Ian Campbell
2004-10-20 15:06 ` Richard B. Johnson
2004-10-21 20:15 ` Sam Ravnborg [this message]
2004-10-21 18:21 ` Richard B. Johnson
2004-10-22 2:54 ` Herbert Poetzl
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=20041021201545.GA16474@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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®