From: Gilad Rom <gilad@romat.com>
To: Clem Taylor <clem.taylor@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: compiling yamon for Au1550 with a recent toolchain?
Date: Mon, 21 Feb 2005 20:15:02 +0200 [thread overview]
Message-ID: <421A2526.6020806@romat.com> (raw)
In-Reply-To: <ecb4efd1050221083348d1f90b@mail.gmail.com>
I have. I can tell you it required a lot of hacking, most of which
I haven't written down.
I can send you my sources if you'd like. They're hardwired for
Au1500/Little Endian, but they build ;)
Shoudn't take long to change the actual build type.
Gilad.
Clem Taylor wrote:
> This isn't completely on topic, but it is a step on the way. I'm
> getting ready for my Au1550 based hardware that will be back from
> assembly soon. I'm trying to get the AMD provided yamon source to
> compile. I'm using gcc 3.4.3 and bintools 2.15.94.0.2. After a few
> tweeks to the makefile, yamon compiles but fails to link:
>
> mips-ld -G 0 -T ./../link/link_el.xn -o ./yamon-02.23DB1550_el.elf -Map ...
> mips-ld: section .data [000000009fc3d650 -> 000000009fc40faf] overlaps
> section .rodata.str1.4 [000000009fc3d650 -> 000000009fc47197]
> mips-ld: ./yamon-02.23DB1550_el.elf: section .rodata.str1.4 lma
> 0x9fc3d650 overlaps previous sections
> mips-ld: ./yamon-02.23DB1550_el.elf: section .rodata.cst4 lma
> 0x9fc47198 overlaps previous sections
>
> The linker command file (bin/link/link_el.xn) puts .data and .rodata
> in _etext. I changed the *(.rodata) to *(.rodata*) in the link_el.xn,
> but that didn't help.
>
> Any ideas what might be going on? Has anyone tried compiling this
> yamon with a recent gcc/bintools?
>
> Thanks,
> Clem
>
>
prev parent reply other threads:[~2005-02-21 18:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 16:33 compiling yamon for Au1550 with a recent toolchain? Clem Taylor
2005-02-21 18:15 ` Gilad Rom [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=421A2526.6020806@romat.com \
--to=gilad@romat.com \
--cc=clem.taylor@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox