From: Sam Ravnborg <sam@ravnborg.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: linuxppc-dev@ozlabs.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.25: pmac_newworld undefined
Date: Tue, 29 Apr 2008 21:17:53 +0200 [thread overview]
Message-ID: <20080429191753.GA32685@uranus.ravnborg.org> (raw)
In-Reply-To: <20080429133514.GA30524@cs181133002.pp.htv.fi>
On Tue, Apr 29, 2008 at 04:35:14PM +0300, Adrian Bunk wrote:
> On Mon, Apr 28, 2008 at 09:33:24PM +0200, Sam Ravnborg wrote:
> > On Mon, Apr 28, 2008 at 02:20:44PM +1000, Tony Breeds wrote:
> > > On Sun, Apr 27, 2008 at 08:03:46PM +0200, Christian Kujau wrote:
> > > > Hi,
> > > >
> > > > the build failure reported[0] by Kamalesh back in 01/2008 is still
> > > > present in today's 2.6.25-git with CONFIG_NVRAM=m (instead of =y):
> > > >
> > > > Building modules, stage 2.
> > > > MODPOST 72 modules
> > > > ERROR: "pmac_newworld" [arch/powerpc/platforms/powermac/nvram.ko] undefined!
> > > > ERROR: "__alloc_bootmem" [arch/powerpc/platforms/powermac/nvram.ko]
> > > > undefined!
> > > > make[1]: *** [__modpost] Error 1
> > >
> > > Yeah that isn't really surprising. Essentially
> > > arch/powerpc/platforms/powermac/nvram.c must be builtin (not modular)
> > > but CONFIG_NVRAM is tristate, and your .config has CONFIG_NVRAM=m.
> > >
> > > We can probably "fix" this by adding another config config symbol and
> > > "selecting" that from CONFIG_NVRAM. Then using this new symbol in
> > > arch/powerpc/platforms/powermac/*
> > >
> > > so I think with we need is:
> > > config NVRAM
> > > bool "..." if PPC32
> > > tristate "..." if !PPC32
> > > ...
> > > ...
> > >
> > > Sam is there some way to achieve that or should we just create an
> > > secondary symbol?
> >
> > In the Makefile you could just do a:
> >
> > obj-$(CONFIG_NVRAM:m=y) += nvram.o
> >
> > Then you would force nvram to be build-in.
> > That looks simpler than messing with Kconfig in this case.
>
> You miss that this is only true on powerpc.
And so is the Makefile - right?
Or is this only true for 32 bit powerpc - in that case it is the wrong fix.
> And for such issues Kconfig anyway is the right place - assume how your
> solution would break if NVRAM would some day select or depend on some
> helper code.
So something like:
config PPC32_NVRAM
bool
depends on NVRAM
obj-$(CONFIG_PPC32_NVRAM) += nvram.o
obj-$(CONFIG_NVRAM) += nvram.o
Or did you have another solution in mind?
Sam
next prev parent reply other threads:[~2008-04-29 19:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 18:03 2.6.25: pmac_newworld undefined Christian Kujau
2008-04-28 4:20 ` Tony Breeds
2008-04-28 19:33 ` Sam Ravnborg
2008-04-29 13:35 ` Adrian Bunk
2008-04-29 19:17 ` Sam Ravnborg [this message]
2008-04-29 19:45 ` Adrian Bunk
2008-04-29 1:42 ` [PATCH] Allow builing of pmac32 when CONFIG_NVRAM=m Tony Breeds
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=20080429191753.GA32685@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).