From: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Recommended MIPS toolchain
Date: Wed, 20 Aug 2014 12:23:38 +0200 [thread overview]
Message-ID: <53F4772A.3080601@gmail.com> (raw)
In-Reply-To: <CA+gZxsP+X-5d0fepDxEndNCyRRDzSjd5jpGcZZ2b2E2=V3QT7w@mail.gmail.com>
On 20.08.2014 11:35, Vasili Galka wrote:
> Hi,
>
> What is the recommended tool-chain to verify compilation of MIPS boards?
you could try
Denx ELDK 5.5 for MIPS
http://www.denx.de/wiki/ELDK-5/WebHome
or
Mentor Sourcery CodeBench Lite Edition for MIPS ELF
https://sourcery.mentor.com/GNUToolchain/subscription3537?lite=MIPS
>
> I tried the one from
> https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.9.0/
> But it does not work, throws plenty of errors about hard/soft float.
Similar to ARM you can use the built-in libgcc implementation of U-Boot
with "export USE_PRIVATE_LIBGCC=yes" (before Kbuild/Kconfig) or
"CONFIG_USE_PRIVATE_LIBGCC=y".
Actually you would need a full multilib toolchain with different libgcc
or multiple toolchains to build all BE/LE and hard-float/soft-float
variants. But that is not feasible, so you should always set
USE_PRIVATE_LIBGCC. USE_PRIVATE_LIBGCC is also required for ELDK toolchains.
BTW: "MAKEALL -a mips" with the kernel.org toolchain and
USE_PRIVATE_LIBGCC works
--
- Daniel
next prev parent reply other threads:[~2014-08-20 10:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 9:35 [U-Boot] Recommended MIPS toolchain Vasili Galka
2014-08-20 10:23 ` Daniel Schwierzeck [this message]
2014-08-20 11:50 ` Vasili Galka
2014-08-20 12:20 ` Daniel Schwierzeck
2014-08-20 12:31 ` Vasili Galka
2014-09-08 9:29 ` Masahiro Yamada
2014-09-08 9:40 ` Vasili Galka
2014-09-08 10:30 ` Daniel Schwierzeck
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=53F4772A.3080601@gmail.com \
--to=daniel.schwierzeck@gmail.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