From: Tom Rini <trini@kernel.crashing.org>
To: Miles Lane <miles.lane@comcast.net>
Cc: paulus@samba.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test2 (Linus tree ppc32 build) -- drivers/built-in.o(.init.text+0x5e64): In function `init_control': undefined reference to `nvram_read_byte'
Date: Tue, 29 Jul 2003 12:04:11 -0700 [thread overview]
Message-ID: <20030729190411.GJ16051@ip68-0-152-218.tc.ph.cox.net> (raw)
In-Reply-To: <200307271801.44966.miles.lane@comcast.net>
On Sun, Jul 27, 2003 at 06:01:44PM -0700, Miles Lane wrote:
> LD .tmp_vmlinux1
> drivers/built-in.o(.init.text+0x5e64): In function `init_control':
> : undefined reference to `nvram_read_byte'
> drivers/built-in.o(.init.text+0x5e64): In function `init_control':
> : relocation truncated to fit: R_PPC_REL24 nvram_read_byte
> drivers/built-in.o(.init.text+0x5ef0): In function `init_control':
> : undefined reference to `nvram_read_byte'
> drivers/built-in.o(.init.text+0x5ef0): In function `init_control':
> : relocation truncated to fit: R_PPC_REL24 nvram_read_byte
> drivers/built-in.o(.init.text+0x67cc): In function `init_platinum':
> : undefined reference to `nvram_read_byte'
> drivers/built-in.o(.init.text+0x67cc): In function `init_platinum':
> : relocation truncated to fit: R_PPC_REL24 nvram_read_byte
> drivers/built-in.o(.init.text+0x67ec): In function `init_platinum':
> : undefined reference to `nvram_read_byte'
> drivers/built-in.o(.init.text+0x67ec): In function `init_platinum':
> : relocation truncated to fit: R_PPC_REL24 nvram_read_byte
> drivers/built-in.o(.init.text+0x7c08): In function `init_imstt':
> : undefined reference to `nvram_read_byte'
> drivers/built-in.o(.init.text+0x7c08): In function `init_imstt':
> : relocation truncated to fit: R_PPC_REL24 nvram_read_byte
> drivers/built-in.o(.init.text+0x7c24): more undefined references to
> `nvram_read_byte' follow
> drivers/built-in.o(.init.text+0x7c24): In function `init_imstt':
> : relocation truncated to fit: R_PPC_REL24 nvram_read_byte
The problem is that arch/ppc/platforms/pmac_nvram.c needs to be compiled
on CONFIG_PPC_PMAC, not on CONFIG_NVRAM (so edit
arch/ppc/platforms/Makefile).
--
Tom Rini
http://gate.crashing.org/~trini/
prev parent reply other threads:[~2003-07-29 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 1:01 2.6.0-test2 (Linus tree ppc32 build) -- drivers/built-in.o(.init.text+0x5e64): In function `init_control': undefined reference to `nvram_read_byte' Miles Lane
2003-07-29 19:04 ` Tom Rini [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=20030729190411.GJ16051@ip68-0-152-218.tc.ph.cox.net \
--to=trini@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@comcast.net \
--cc=paulus@samba.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).