From: David Daney <ddaney@caviumnetworks.com>
To: Andreas Barth <aba@not.so.argh.org>
Cc: linux-mips@linux-mips.org
Subject: Re: Problems and workarounds while building octeon kernels
Date: Mon, 22 Feb 2010 13:24:32 -0800 [thread overview]
Message-ID: <4B82F610.8070105@caviumnetworks.com> (raw)
In-Reply-To: <20100220175125.GQ27216@mails.so.argh.org>
On 02/20/2010 09:51 AM, Andreas Barth wrote:
> Hi,
>
> I tried to build an recent linux 2.6.33-rc something in an unstable
> Debian chroot. I had the following issues (plus workarounds / fixes) -
> please don't hesitate to ask me if you have further questions.
>
I have a questions:
* Were you able to produce a *bootable* kernel after your workarounds?
* What did your make invocation look like?
The reason I ask it that you are using a compiler that defaults to
little-endian and 32-bit. Unless you did something to override these
defaults, I would be surprised if you obtained something bootable.
David Daney
>
> error:
> arch/mips/cavium-octeon/built-in.o: In function `prom_init':
> (.init.text+0x974): undefined reference to `early_serial_setup'
> arch/mips/cavium-octeon/built-in.o: In function `prom_init':
> (.init.text+0x974): relocation truncated to fit: R_MIPS_26 against `early_serial_setup'
> arch/mips/cavium-octeon/built-in.o: In function `flash_init':
>
> fix: enabled configuration for serial console support
>
>
> error:
> flash_setup.c:(.init.text+0x12dc): undefined reference to `simple_map_init'
> flash_setup.c:(.init.text+0x12dc): relocation truncated to fit: R_MIPS_26 against `simple_map_init'
> flash_setup.c:(.init.text+0x12ec): undefined reference to `do_map_probe'
> flash_setup.c:(.init.text+0x12ec): relocation truncated to fit: R_MIPS_26 against `do_map_probe'
> flash_setup.c:(.init.text+0x1314): undefined reference to `parse_mtd_partitions'
> flash_setup.c:(.init.text+0x1314): relocation truncated to fit: R_MIPS_26 against `parse_mtd_partitions'
> flash_setup.c:(.init.text+0x1330): undefined reference to `add_mtd_partitions'
> flash_setup.c:(.init.text+0x1330): relocation truncated to fit: R_MIPS_26 against `add_mtd_partitions'
> flash_setup.c:(.init.text+0x1340): undefined reference to `add_mtd_device'
> flash_setup.c:(.init.text+0x1340): relocation truncated to fit: R_MIPS_26 against `add_mtd_device'
>
> fix: set drivers/mtd to y (instead of m)
>
>
>
> error:
> arch/mips/cavium-octeon/built-in.o: In function `sched_clock':
> (.text.sched_clock+0x24): undefined reference to `__lshrti3'
> arch/mips/cavium-octeon/built-in.o: In function `sched_clock':
> (.text.sched_clock+0x24): relocation truncated to fit: R_MIPS_26 against `__lshrti3'
>
> workaround: in arch/mips/cavium-octeon/csrc-octeon.c
> #if (__GNUC__< 4) || ((__GNUC__ == 4)&& (__GNUC_MINOR__<= 3))
> replaced by something that always uses "the ugly way"
>
>
> ERROR: "i8253_lock" [drivers/input/misc/pcspkr.ko] undefined!
> fix: disable pc speaker support
>
>
> Cheers,
> Andi
>
>
next prev parent reply other threads:[~2010-02-22 21:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-20 17:51 Problems and workarounds while building octeon kernels Andreas Barth
2010-02-22 17:42 ` David Daney
2010-02-22 20:25 ` Andreas Barth
2010-02-22 20:55 ` David Daney
2010-02-22 21:03 ` Andreas Barth
2010-02-22 21:24 ` David Daney [this message]
2010-02-23 23:47 ` Andreas Barth
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=4B82F610.8070105@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=aba@not.so.argh.org \
--cc=linux-mips@linux-mips.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.