From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ARC: bump tools to 2014.12 release
Date: Wed, 4 Mar 2015 12:03:58 +0100 [thread overview]
Message-ID: <20150304120358.591484a9@free-electrons.com> (raw)
In-Reply-To: <1422879584-18485-1-git-send-email-abrodkin@synopsys.com>
Dear Alexey Brodkin,
On Mon, 2 Feb 2015 15:19:44 +0300, Alexey Brodkin wrote:
> Now when new shiny tools are released by Synopsys we're ready for
> version update in Buildroot again.
>
> More details about arc-2014.12 release are available here:
> https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/releases/tag/arc-2014.12
>
> Following patches were removed from GCC since they are a part of release
> now:
> * 200-size_type_unsigned_int.patch
> * 300-ptrdiff_type_int.patch
> * 400-call-arc_hazard-before-branch-shortening.patch
> * 401-fix-length-attribute-for-casesi_load-pattern.patch
> * 402-fix-length-of-instructions-that-are-in-delay-slot-and-needs-to-be-predicated.patch
> * 403-update-casesi_compact_jump-instruction-length.patch
>
> But since arc-2014.12 tools are still based on GCC 4.8 following patches
> ar still relevant so moving to the new folder to match ARC gcc bump.
> * 100-libstdcxx-uclibc-c99.patch
> * 910-gcc-poison-system-directories.patch
>
> Binutils are still based on 2.23 so following patch still makes sense:
> * 600-poison-system-directories.patch
>
> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
>
> Cc: Anton Kolesov <akolesov@synopsys.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Cc: Peter Korsgaard <peter@korsgaard.com>
It seems like the update of GDB for ARC is causing some build problems:
http://autobuild.buildroot.org/results/d62/d62f472d70f60281dfe94cffc46a3e0566fd4a3d/build-end.log
It's trying to build a shared libbfd.so using a statically compiled
libiberty.a which wasn't built with -fPIC. I don't know if the problem
is specific to ARC GDB or not.
Can you have a look?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-04 11:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 12:19 [Buildroot] [PATCH] ARC: bump tools to 2014.12 release Alexey Brodkin
2015-02-02 20:28 ` Thomas Petazzoni
2015-03-04 11:03 ` Thomas Petazzoni [this message]
2015-03-13 7:18 ` Alexey Brodkin
2015-03-13 8:19 ` Romain Naour
2015-03-13 9:00 ` Alexey Brodkin
2015-03-13 9:10 ` Romain Naour
2015-03-24 13:51 ` Alexey Brodkin
2015-03-24 15:31 ` Thomas Petazzoni
2015-03-24 16:03 ` Alexey Brodkin
2015-04-05 21:53 ` Romain Naour
2015-04-06 20:29 ` Romain Naour
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=20150304120358.591484a9@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox