From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] linking u-boot for mips little endian w/ hardhat tools.
Date: Fri, 08 Oct 2004 22:28:14 +0200 [thread overview]
Message-ID: <20041008202819.8D2BFC1430@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 08 Oct 2004 11:26:38 PDT." <200410081126.38970.msundius@sundius.com>
In message <200410081126.38970.msundius@sundius.com> you wrote:
>
> OUTPUT_FORMAT("elf32-tradlittlemips", "elf32-tradlittlemips",\
> "elf32-tradlittlemips")
> if changed to:
> OUTPUT_FORMAT("elf32-tradbigmips", "elf32-tradbigmips", "elf32-tradbigmips")
> will allow me to compile and link fine...
>
> my question is then:
>
> 1) what does this really do?
Maybe it changes the output format from little endian to big endian?
> 2) if I'm using a little endian cpu, do I really need it set to
> elf32-tradlittlemips?
Depending on your toolchain, yes.
> 3) if so how do I solve my problem?
Use different tools?
> 4) if not why?
Why what?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de
It is dangerous to be right on a subject on which the established
authorities are wrong. -- Voltaire
next prev parent reply other threads:[~2004-10-08 20:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1CBqxq-0002xy-46@sc8-sf-list1.sourceforge.net>
2004-09-29 18:50 ` [U-Boot-Users] size of mips U-boot image C Michael Sundius
2004-09-29 19:42 ` Wolfgang Denk
2004-10-08 18:26 ` [U-Boot-Users] linking u-boot for mips little endian w/ hardhat tools C Michael Sundius
2004-10-08 18:54 ` Charles Eidsness
2004-10-08 20:28 ` Wolfgang Denk [this message]
2004-10-09 1:07 ` Masami Komiya
2004-10-11 22:53 ` Wolfgang Denk
2004-10-12 0:06 ` Masami Komiya
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=20041008202819.8D2BFC1430@atlas.denx.de \
--to=wd@denx.de \
--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