[Buildroot] [PATCH 2/5] gcc: add microblaze internal toolchain

Spenser Gilliland spenser at gillilanding.com
Tue Nov 5 02:48:47 UTC 2013


Thomas,

Haven't had a chance to work on this yet but should have time this week.

Spenser
On Nov 1, 2013 11:24 AM, "Thomas Petazzoni" <
thomas.petazzoni at free-electrons.com> wrote:

> Dear Spenser Gilliland,
>
> On Mon, 14 Oct 2013 17:55:17 -0500, Spenser Gilliland wrote:
>
> > > On Fri, 11 Oct 2013 09:33:17 -0500, Spenser Gilliland wrote:
> > >
> > > > @@ -102,6 +108,7 @@ config BR2_GCC_VERSION
> > > >       default "4.7.3"     if BR2_GCC_VERSION_4_7_X
> > > >       default "4.8.1"     if BR2_GCC_VERSION_4_8_X
> > > >       default "4.8-arc"   if BR2_GCC_VERSION_4_8_ARC
> > > > +     default "4.9-microblaze" if BR2_GCC_VERSION_4_9_MICROBLAZE
> > > >       default $BR2_GCC_SNAP_DATE if BR2_GCC_VERSION_SNAP
> > >
> > > I'm getting a build failure while testing this patch set:
> > >
> > > >>> host-gcc-final 4.9-microblaze Patching package/gcc//gcc-final
> > > support/scripts/apply-patches.sh
> > /home/test/outputs/microblaze-glibc/build/host-gcc-final-4.9-microblaze
> > package/gcc/4.9-microblaze \*.patch
> > > Aborting.  'package/gcc/4.9-microblaze' is not a directory.
> > >
> > > I believe we should have a few patches, at least the ones that are also
> > > in package/gcc/4.8-arc.
> > >
> > > Is this something you are willing to fix, or should I take your patches
> > > and fix those problems?
> >
> > Yes, I'll take a look at it tomorrow.
>
> Any news?
>
> Thanks,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20131104/9cdb87c8/attachment-0002.html>


More information about the buildroot mailing list