From: tony@bakeyournoodle•com (Tony Breeds)
To: Christian Kujau <lists@nerdbynature•de>, Sam Ravnborg <sam@ravnborg•org>
Cc: linuxppc-dev@ozlabs•org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: 2.6.25: pmac_newworld undefined
Date: Mon, 28 Apr 2008 14:20:44 +1000 [thread overview]
Message-ID: <20080428042044.GX20457@bakeyournoodle.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0804271951190.11017@sheep.housecafe.de>
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?
Yours Tony
linux.conf.au http://www.marchsouth.org/
Jan 19 - 24 2009 The Australian Linux Technical Conference!
next prev parent reply other threads:[~2008-04-28 4:20 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 [this message]
2008-04-28 19:33 ` Sam Ravnborg
2008-04-29 13:35 ` Adrian Bunk
2008-04-29 19:17 ` Sam Ravnborg
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=20080428042044.GX20457@bakeyournoodle.com \
--to=tony@bakeyournoodle$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=lists@nerdbynature$(echo .)de \
--cc=sam@ravnborg$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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