From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/5] gcc: add microblaze internal toolchain
Date: Fri, 1 Nov 2013 19:24:10 +0100 [thread overview]
Message-ID: <20131101192410.6a7875a3@skate> (raw)
In-Reply-To: <CAEBucnAb7nqvgqTMv9s0HJYSL5R_GRBS+Gz2HHDo31G7fsvPAg@mail.gmail.com>
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 prev parent reply other threads:[~2013-11-01 18:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 14:33 [Buildroot] [PATCH 0/5] Add Microblaze internal toolchain Spenser Gilliland
2013-10-11 14:33 ` [Buildroot] [PATCH 1/5] binutils: add microblaze " Spenser Gilliland
2013-10-11 14:33 ` [Buildroot] [PATCH 2/5] gcc: " Spenser Gilliland
2013-10-13 10:40 ` Thomas Petazzoni
2013-10-14 22:55 ` Spenser Gilliland
2013-10-15 8:17 ` Thomas Petazzoni
2013-11-01 18:24 ` Thomas Petazzoni [this message]
2013-11-05 2:48 ` Spenser Gilliland
2013-10-11 14:33 ` [Buildroot] [PATCH 3/5] glibc: " Spenser Gilliland
2013-10-11 14:33 ` [Buildroot] [PATCH 4/5] gdb: " Spenser Gilliland
2013-10-11 14:33 ` [Buildroot] [PATCH 5/5] toolchain: enable microblaze toolchain Spenser Gilliland
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=20131101192410.6a7875a3@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.