All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] Installing gcc commpiler on openrisc linux
Date: Thu, 25 Aug 2016 16:15:26 +0900	[thread overview]
Message-ID: <CAAfxs74Mvmh1Q-tQXtDfwHE_EpE-Ecs9fjQ=JUNhfw-W+ghALA@mail.gmail.com> (raw)
In-Reply-To: <ab2639ae-6747-ce88-edc3-559700c4b45c@wallentowitz.de>

Hello,

There are two ways.

1.
When building the Linux kernel you can place any files you want under /arch
<https://github.com/openrisc/linux/tree/master/arch>/openrisc
<https://github.com/openrisc/linux/tree/master/arch/openrisc>/support
<https://github.com/openrisc/linux/tree/master/arch/openrisc/support>/
*initramfs* and they will be there when you buy the system.

2. Not got this working myself
When you connect to your serial terminal there are ways to transfer through
the serial connection. You can maybe get builds of zmodem working there.

-Stafford

On 25 Aug 2016 4:13 p.m., "Stefan Wallentowitz" <stefan@wallentowitz.de>
wrote:

> On 25.08.2016 01:44, Stafford Horne wrote:
> > Hello Manaar,
> >
> > The openrisc Linux build creates an image with all the tools provided
> > using busybox (it's in the kernel source tree). So it's basically a
> > busybox embedded system.  You can Google about adding gcc or another c
> > compiler to busybox for details.
> >
> > I don't think it's been done before. Gcc is rather large for de0 nano
> > ;it's not just gcc but linkers and assemblers and libraries you would
> > want to link in. However, I wouldnt bet it's impossible if you strip it
> > down.
> >
> > -Stafford
>
> Hi Manaar,
>
> just to add to this and Jeremy's comment: It is not the standard way to
> compile inside the target system. Instead you cross-compile on your host
> and transfer the binary ELF to the target.
>
> I am not sure if the tutorial already covers adding files to the ramdisk
> (the image you load onto the target). Stafford, you are the expert on
> this, right?
>
> Cheers,
> Stefan
>
>
>
> _______________________________________________
> OpenRISC mailing list
> OpenRISC at lists.librecores.org
> https://lists.librecores.org/listinfo/openrisc
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.librecores.org/pipermail/openrisc/attachments/20160825/12fafe83/attachment.html>

  reply	other threads:[~2016-08-25  7:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-24 23:03 [OpenRISC] Installing gcc commpiler on openrisc linux Manaar Alam
2016-08-24 23:44 ` Stafford Horne
2016-08-25  7:03   ` Jeremy Bennett
2016-08-25  7:13   ` Stefan Wallentowitz
2016-08-25  7:15     ` Stafford Horne [this message]
     [not found]   ` <CAFoY_ww=jonkgne6xTis6EvGLJFGTnw_O=HEhCbNZnvQFutO8A@mail.gmail.com>
     [not found]     ` <CAAfxs77h1CeyF2awfWOrKDdGmVW2aGinJPAF_CatfMF4KdWKLg@mail.gmail.com>
2016-08-25  7:19       ` Stafford Horne
2016-08-25  8:15         ` Jeremy Bennett

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='CAAfxs74Mvmh1Q-tQXtDfwHE_EpE-Ecs9fjQ=JUNhfw-W+ghALA@mail.gmail.com' \
    --to=shorne@gmail.com \
    --cc=openrisc@lists.librecores.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.