All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Christoph Hellwig <hch@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: kbuild: shorthand ym2y, ym2m etc
Date: Sun, 30 Jan 2005 22:44:52 +0000	[thread overview]
Message-ID: <20050130224452.G25000@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20050130223926.GG14816@mars.ravnborg.org>; from sam@ravnborg.org on Sun, Jan 30, 2005 at 11:39:26PM +0100

On Sun, Jan 30, 2005 at 11:39:26PM +0100, Sam Ravnborg wrote:
> On Sun, Jan 30, 2005 at 07:52:30PM +0000, Christoph Hellwig wrote:
> > 
> > obj-$(CONFIG_FB)$(CONFIG_PPC)		+= macmodes.o
> > 
> > would be a lot more obvious, but I'm not sure how to handle
> > it for the case where one of them evaluates to m
> 
> The real problem is when say CONFIG_FB are empty. Then kbuild will see:
> obj-$(CONFIG_PPC) which I doubt was what you wanted.
> 
> This can be fixed by changing Kconfig to evaluate all known symbols to
> either y,m,n - in contradiction to today where symbols that evaluate
> to n is left empty.

Isn't that rather hard to achieve, unless all Kconfig files (including
all architecture specific ones) are read?  Eg, CONFIG_PPC wouldn't
exist on ARM.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

  reply	other threads:[~2005-01-30 22:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-30 19:37 kbuild: shorthand ym2y, ym2m etc Sam Ravnborg
2005-01-30 19:48 ` Muli Ben-Yehuda
2005-01-30 19:52 ` Christoph Hellwig
2005-01-30 22:39   ` Sam Ravnborg
2005-01-30 22:44     ` Russell King [this message]
2005-01-30 22:51       ` Sam Ravnborg
2005-01-30 22:41 ` Arnd Bergmann
2005-01-30 22:59   ` Sam Ravnborg
2005-01-31  1:57 ` Andreas Gruenbacher

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=20050130224452.G25000@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.