mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Franck Jullien <franck.jullien@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox <barebox@lists.infradead.org>
Subject: Re: openrisc build problem
Date: Mon, 9 Feb 2015 12:26:05 +0100	[thread overview]
Message-ID: <CAJfOKBx-KuUdPfQXeC9xCM7wFugBuo7i8dj7cBqGBXtSFQ4n6A@mail.gmail.com> (raw)
In-Reply-To: <20150209074034.GT12209@pengutronix.de>

2015-02-09 8:40 GMT+01:00 Sascha Hauer <s.hauer@pengutronix.de>:
> Hi,
>
> On Sun, Feb 08, 2015 at 08:35:40PM +0100, Franck Jullien wrote:
>>
>> Hi,
>>
>> Yes I know :) Until now, the official openrisc toolchain was called or32.
>> However, the new one (and maintained one)  is called or1k. So we need
>> to change "elf32-or32" to "elf32-or1k" in barebox.lds.S.
>>
>> Feel free to send a patch. Or I'll do that later.
>
> Is there a binary toolchain somewhere for download? I'll need for my
> build tests once this patch is in.
>

Here: http://opencores.org/or1k/OpenRISC_GNU_tool_chain#Prebuilt_versions
Or more recent here:
http://lis.ei.tum.de/pub-download/openrisc-builds/or1k-elf/release/

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2015-02-09 11:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-08 19:26 Antony Pavlov
2015-02-08 19:35 ` Franck Jullien
2015-02-09  7:40   ` Sascha Hauer
2015-02-09 11:26     ` Franck Jullien [this message]
2015-02-09 11:49       ` Antony Pavlov
2015-02-09 19:24         ` Franck Jullien
2015-02-10 23:16           ` Antony Pavlov
2015-02-11  9:44             ` Sascha Hauer
2015-02-13 19:06             ` 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=CAJfOKBx-KuUdPfQXeC9xCM7wFugBuo7i8dj7cBqGBXtSFQ4n6A@mail.gmail.com \
    --to=franck.jullien@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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