From: Ronen Shitrit <rshitrit@il.marvell.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] MIPS (purple) compilation problems.
Date: Tue, 16 Mar 2004 18:03:58 +0200 [thread overview]
Message-ID: <4057256E.3080604@il.marvell.com> (raw)
In-Reply-To: 404DBFBF.50808@il.marvell.com
Hi
I'm trying to port the U-Boot to Marvell board with MIPS (rm7000)
I see that after relocating to the DRAM the disassembly of the u-boot
shows me
that we jump back to the flash:
start.S: dis:
la t9,board_init_r lui t9,0xbfc1
addiu t9,20140
j t9 jr t9
I see that I get the same problem when I jump to printf etc.
maybe it is because I don't compile the code as PIC? Is there any
special compilation flag I should use?
Can someone please send me a disassembly of the U-Boot for any of the
MIPS board (purple, incaip or dbaux100).
Is there any special handle for relocating of the MIPS that is different
from the PPC, that I should take under consideration???
Thanks Ronen
Ronen Shitrit wrote:
> Hi
>
> I'm trying to port the U-Boot to Marvell board with MIPS (rm7000)
> I am using a cross compiler mips64-elf.
> I'm trying to compile the purpule_config and I have some compilation
> problems,
> when I'm using the cpu/mips/config flag -mabicalls I get a lot of
> warnings:
> c1: warning: -G is incompatible with PIC code which is the default
> .........
> and an LD error:
> mips64-elf-ld: common/main.o: linking PIC files with non-PIC files
> Bad value: failed to merge target specific data of file
> common/main.o
>
> When I remove the -mabicalls flag, the compilation pass, and the LD
> fail again on different error:
> mips64-elf-ld: target elf32-tradbigmips not found
>
> The LD is looking for elf32-tradbigmips because in the LD script we
> define the output file to be: elf32-tradbigmips
>
> why do we use this definition and not elf32-bigmips?? and what is the
> difference between these two??
> and why when I install my cross compiler I don't have support for this
> output format??
>
> so I changed it the output format to elf32-bigmips then I'm getting
> this LD error:
> : undefined reference to `_GLOBAL_OFFSET_TABLE_'
>
> I know it is because I don't have this define in the linker script,
> and I guess the elf32-tradbigmips has this definition.
> What should I do??
>
> Thanks
>
--
Ronen Shitrit
M.S.I.L
D.N. Misgav 20184
Tel: +972-4-9951000
Fax: +972-4-9951001
Email: mailto: ronen.shitrit at il.marvell.com
_____________________________________________________________
This message may contain confidential, proprietary or legally privileged
information. The information is intended only for the use of the individual
or entity named above. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution
or copying of this communication is strictly prohibited. If you have
received this communication in error, please notify us immediately by
telephone, or by e-mail and delete the message from your computer.
next prev parent reply other threads:[~2004-03-16 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 12:59 [U-Boot-Users] MIPS (purple) compilation problems Ronen Shitrit
2004-03-16 16:03 ` Ronen Shitrit [this message]
2004-03-16 17:47 ` Wolfgang Denk
2004-03-17 13:32 ` Ronen Shitrit
2004-03-17 21:07 ` Wolfgang Denk
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=4057256E.3080604@il.marvell.com \
--to=rshitrit@il.marvell.com \
--cc=u-boot@lists.denx.de \
/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