From: Oleksij Rempel <linux@rempel-privat.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: MIPS multiimabe is brocken after "Images: Add image size to built images"
Date: Sat, 22 Dec 2018 11:03:56 +0100 [thread overview]
Message-ID: <a1fbae3e-1b53-49fc-04ec-4b581557c0af@rempel-privat.de> (raw)
In-Reply-To: <20181222100043.GA9339@ravnborg.org>
Am 22.12.18 um 11:00 schrieb Sam Ravnborg:
> On Sat, Dec 22, 2018 at 10:56:56AM +0100, Sam Ravnborg wrote:
>> Hi Oleksij
>>
>>> i can't build MIPS images after this patch:
>>>
>>> commit 3abeee3e45224c73245e32cb614c241cd195f1c4 (bb/master)
>>> Author: Sascha Hauer <s.hauer@pengutronix.de>
>>> Date: Mon Dec 17 12:09:23 2018 +0100
>>
>> Can you elaborate a little what goes wrong.
>> Does the build fail or you cannot boot barebox?
>
> If I want to try to build a mips variant of barebox,
> can you then recommend a toolchain to use?
>
> Maybe one from:
> https://toolchains.bootlin.com/
> ?
Mostly I use native toolchain provided by debian/ubuntu
mips-linux-gnu-gcc
As alternative i also use toolchain provided by pengutronix:
https://www.pengutronix.de/de/software/toolchain.html
https://debian.pengutronix.de/
package: oselas.toolchain-2018.12-mips-softfloat-linux-gnu
--
Regards,
Oleksij
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-12-22 10:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-22 9:12 Oleksij Rempel
2018-12-22 9:56 ` Sam Ravnborg
2018-12-22 10:00 ` Sam Ravnborg
2018-12-22 10:03 ` Oleksij Rempel [this message]
2018-12-31 10:07 ` Sam Ravnborg
2018-12-22 10:00 ` Oleksij Rempel
2019-01-03 10:04 ` Sascha Hauer
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=a1fbae3e-1b53-49fc-04ec-4b581557c0af@rempel-privat.de \
--to=linux@rempel-privat.de \
--cc=barebox@lists.infradead.org \
--cc=sam@ravnborg.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