All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] Toolchain for Microblaze
Date: Mon, 12 Mar 2012 18:17:47 +0100	[thread overview]
Message-ID: <4F5E2FBB.3080407@relinux.de> (raw)
In-Reply-To: <CAEBucnBDBsHffFp=FZ5rkzN-ubrNLr_2U=_dQAtKe6AuuQg_tQ@mail.gmail.com>

Am 12.03.2012 02:37, schrieb Spenser Gilliland:
> I agree it would be nice. Although, I have tried to get this to work
> with no success.  The following repos may be of some help (have not
> had time to test them.)
>
> http://git.monstr.eu/git/
>
> Spenser
I just thought about trying this old 4.1.2 version when I found out that
gnu now supports Microblaze in 4.6. I hope someone familiar in building
toolchains can help building it.

Stephan
> On Sun, Mar 11, 2012 at 1:26 PM, Stephan Hoffmann <sho@relinux.de> wrote:
>> Hello all,
>>
>> I just found on the gcc web site ( http://gcc.gnu.org/gcc-4.6/changes.html )
>> the following message:
>>
>> MicroBlaze
>>
>> Support has been added for the Xilinx MicroBlaze softcore processor
>> (microblaze-elf) embedded target. This configurable processor is supported
>> on several Xilinx Spartan and Virtex FPGAs.
>>
>> This sounds like good news. Maybe we can get rid of the prebuild Xilinx
>> Toolchain.
>>
>> Unfortunatelly, I don't have any experience in building toolchains. A first
>> try building it as internal toolchain with almost standard settings ended
>> with an aclocal error;-(
>>
>> Can anyone try building it?
>>
>> Kind regards
>>
>> Stephan
>>
>> --
>> reLinux     -    Stephan Hoffmann
>> Am Schmidtgrund 124    50765 K?ln
>> Tel. +49.221.95595-19    Fax: -64
>> www.reLinux.de     sho at reLinux.de
>>
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
>
>


-- 
reLinux     -    Stephan Hoffmann
Am Schmidtgrund 124    50765 K?ln
Tel. +49.221.95595-19    Fax: -64
www.reLinux.de     sho at reLinux.de

      parent reply	other threads:[~2012-03-12 17:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-11 18:26 [Buildroot] Toolchain for Microblaze Stephan Hoffmann
     [not found] ` <CAEBucnBDBsHffFp=FZ5rkzN-ubrNLr_2U=_dQAtKe6AuuQg_tQ@mail.gmail.com>
2012-03-12  2:20   ` Spenser Gilliland
2012-03-12 17:17   ` Stephan Hoffmann [this message]

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=4F5E2FBB.3080407@relinux.de \
    --to=sho@relinux.de \
    --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 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.