All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Help to fix Microblaze issues in Buildroot
Date: Wed, 20 Nov 2013 11:41:12 +0100	[thread overview]
Message-ID: <20131120114112.03abac2f@skate> (raw)
In-Reply-To: <CAM+bi4sKAyBrLjAKfBBkDMVDLReBHffqUCfdDvU61X1wErLfNA@mail.gmail.com>

Dear Alvaro Gamez,

On Wed, 20 Nov 2013 11:36:00 +0100, Alvaro Gamez wrote:

> Now that I take the time to revisit Xilinx' website, I think maybe
> we're doing something wrong...
> 
> Old Xilinx git repository,
> http://git.xilinx.com/?p=microblaze-gnu.git;a=tree;f=binaries now
> redirect to github: https://github.com/xilinx and seems to be quite
> up to date with upstream gcc.

These repositories are exactly the repositories that Spenser patches
are using for the internal toolchain backend.

See:

  http://patchwork.ozlabs.org/patch/291045/ (binutils)
  http://patchwork.ozlabs.org/patch/291046/ (gcc)
  http://patchwork.ozlabs.org/patch/291047/ (glibc)
  http://patchwork.ozlabs.org/patch/291048/ (gdb)

> There seems to be also a later version of GNU Tools available at
> http://www.xilinx.com/guest_resources/gnu/
> 
>    - GNU Tools for MicroBlaze (gcc 4.6.4, gdb 7.6.0, binutils 2.23.2,
>    newlib 1.19, eglibc-2.18) -
> mb_gnu_20131023.tar.gz<http://www.xilinx.com/guest_resources/member/mb_gnu/mb_gnu_20131023.tar.gz>
> 
> I don't know how up to date are these downloads, but it may be worth
> a try? Although if we're going ahead with Spenser's patches maybe we
> can/(want to?) avoid Xilinx altogether?

We are not avoiding Xilinx altogether at all, please look at Spenser
patches.

*However* the tarballs you're pointing at at
http://www.xilinx.com/guest_resources/gnu/ look interesting for
pre-built external toolchains. I'm currently downloading "GNU Tools for
MicroBlaze (gcc 4.6.4, gdb 7.6.0, binutils 2.23.2, newlib 1.19,
eglibc-2.18)", and I'll have a look at what it is exactly.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2013-11-20 10:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-06 16:54 [Buildroot] Help to fix Microblaze issues in Buildroot Thomas Petazzoni
     [not found] ` <CAM+bi4vGmKHRA3j0ua-dsOBzTuj-BPrM2+z3papeyfDjjazhgw@mail.gmail.com>
2013-11-20 10:03   ` Alvaro Gamez
2013-11-20 10:10     ` Thomas Petazzoni
2013-11-20 10:28       ` Thomas De Schampheleire
2013-11-20 10:32         ` Alvaro Gamez
2013-11-20 10:36       ` Alvaro Gamez
2013-11-20 10:41         ` Thomas Petazzoni [this message]
2013-11-20 12:40           ` Spenser Gilliland
2013-11-20 13:56           ` Alvaro Gamez
2013-11-20 14:00             ` Spenser Gilliland
2013-11-20 14:09             ` Thomas Petazzoni
2013-11-20 14:15               ` Alvaro Gamez
2013-11-20 14:18                 ` Thomas Petazzoni

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=20131120114112.03abac2f@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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.