mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox <barebox@lists.infradead.org>
Subject: Re: openrisc build problem
Date: Wed, 11 Feb 2015 10:44:50 +0100	[thread overview]
Message-ID: <20150211094450.GM12209@pengutronix.de> (raw)
In-Reply-To: <20150211031646.4c6aaf0b21d3cd01883950a3@gmail.com>

On Wed, Feb 11, 2015 at 03:16:46AM +0400, Antony Pavlov wrote:
> On Mon, 9 Feb 2015 20:24:20 +0100
> Franck Jullien <franck.jullien@gmail.com> wrote:
> 
> > 2015-02-09 12:49 GMT+01:00 Antony Pavlov <antonynpavlov@gmail.com>:
> > > On Mon, 9 Feb 2015 12:26:05 +0100
> > > Franck Jullien <franck.jullien@gmail.com> wrote:
> > >
> > >> 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/
> > >
> > >
> > > Hmmm.
> > >
> > > It looks like gcc-or1k-elf-4.8.1-x86_64 does not work on my amd64 Debian testing
> > > ('apt-cache search libmpc2' gives no results). E.g.
> > >
> > >
> > > $ /opt/gcc-or1k-elf-4.8.1-x86_64/bin/or1k-elf-gcc 1.c
> > > /opt/gcc-or1k-elf-4.8.1-x86_64/bin/../libexec/gcc/or1k-elf/4.8.1/cc1: error while loading shared libraries: libmpc.so.2: cannot open shared object file: No such file or directory
> > >
> > > --
> > > Best regards,
> > >   Antony Pavlov
> > 
> > To be honest, I never tried those prebuilt toolchain.
> > Did you try the newer version present on the second link ?
> > 
> 
> Sorry, I have forgotten this question.
> 
> This toolchain works fine:
>   http://lis.ei.tum.de/pub-download/openrisc-builds/or1k-elf/release/or1k-elf-latest-ubuntu-14.04-amd64.tgz

The server seems to be offline for the whole morning now. I'll try
later.

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

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

  reply	other threads:[~2015-02-11  9:45 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
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 [this message]
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=20150211094450.GM12209@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.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