From: Michael Krufky <mkrufky@m1k.net>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: [HOWTO] set extra_cflags to indicate compilation against -mm kernels
Date: Sun, 31 Jul 2005 10:05:53 -0400 [thread overview]
Message-ID: <42ECDAC1.5050305@m1k.net> (raw)
In-Reply-To: <20050731084406.GA8588@mars.ravnborg.org>
Sam Ravnborg wrote:
>On Sat, Jul 30, 2005 at 05:29:21PM -0400, Michael Krufky wrote:
>
>
>>With the addition of topdir-mm.patch into the -mm tree (since
>>2.6.13-rc3-mm2), it is now possible for Makefile to detect whether a cvs
>>subtree is being built against -mm or not... -mm kernels now have a .mm
>>file in the top level directory.
>>
>>inside Makefile:
>>
>>mm-kernel := $(TOPDIR)/.mm
>>ifneq ($(mm-kernel),)
>>MM_KERNEL_CFLAGS := -DMM_KERNEL=$(shell cat $(mm-kernel) 2> /dev/null)
>>ifneq ($(MM_KERNEL_CFLAGS),-DMM_KERNEL=)
>>EXTRA_CFLAGS += $(MM_KERNEL_CFLAGS)
>>endif
>>endif
>>
>>
>
>Hi Michael.
>The content of the .mm file seems to be insignificant - '1'. The important
>issue is that the file is present.
>Also please do not use $(TOPDIR) - it is deprecated.
>
>The following is enough:
>EXTRA_CFLAGS += $(if $(wildcard $(srctree)/.mm), -DMM_KERNEL)
>
>If the file exist in the root of the kernel src tree MM_KERNEL will be
>added to EXTRA_CFLAGS.
>
Sam-
Thank you! I knew there might be a more efficient way to do that, so
I'm glad I sent that to LKML for you to see ;-)
Still, I think it should be added into the documentation somewhere...
I'd be happy to submit a patch, I just don't know where it should go.
Obviously, this is specific to -mm kernels only. Do you know?
--
Michael Krufky
prev parent reply other threads:[~2005-07-31 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 21:29 [HOWTO] set extra_cflags to indicate compilation against -mm kernels Michael Krufky
2005-07-31 8:44 ` Sam Ravnborg
2005-07-31 14:05 ` Michael Krufky [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=42ECDAC1.5050305@m1k.net \
--to=mkrufky@m1k.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
/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