From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] external-toolchain: Allow MIPS64 for Codesourcery MIPS toolchains
Date: Mon, 27 May 2013 11:18:29 +0200 [thread overview]
Message-ID: <20130527111829.42368807@skate> (raw)
In-Reply-To: <CAG2jQ8hK4nY2mL4PQEX8miQyCZLbvV=H9scJu8ZaQPNZnnruNw@mail.gmail.com>
Dear Markos Chandras,
On Mon, 27 May 2013 10:05:10 +0100, Markos Chandras wrote:
> I did limited testing and I haven't seen this problem but I haven't
> build busybox to be honest.
> However, on the release notes they say they support MIPS64/n64
> https://sourcery.mentor.com/GNUToolchain/release2358?@template=datasheet
>
> so I just allowed buildroot to select this combination as well.
>
> My understanding is that the compilation problem is orthogonal to
> mip64/n64 patch in the sense
> that forbidding the combination just hides the problem for now :)
I agree that the problem is orthogonal, but having an external
toolchain that isn't even capable of building Busybox worries me a
little bit. This means that an user selecting mips64 and external
toolchain, and keep all the other options as default, will see a
failing build. Not really nice.
We have various issues with the toolchain from Mentor Graphics. It
would be nice if we could have some contact to help solve those issues.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-05-27 9:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 14:22 [Buildroot] [PATCH] external-toolchain: Allow MIPS64 for Codesourcery MIPS toolchains Markos Chandras
2013-05-26 13:29 ` Thomas Petazzoni
2013-05-27 9:05 ` Markos Chandras
2013-05-27 9:18 ` Thomas Petazzoni [this message]
2013-05-27 15:11 ` Markos Chandras
2013-06-07 8:53 ` Markos Chandras
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=20130527111829.42368807@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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