From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/4] Fix lttng-tools build issue
Date: Mon, 14 Apr 2014 22:42:20 +0200 [thread overview]
Message-ID: <20140414224220.68a5b2fb@skate> (raw)
In-Reply-To: <1397419138-8776-1-git-send-email-thomas.petazzoni@free-electrons.com>
Dear Thomas Petazzoni,
On Sun, 13 Apr 2014 21:58:54 +0200, Thomas Petazzoni wrote:
> Hello,
>
> This set of patches fix the lttng-tools build issue with gcc 4.7.x and
> gcc 4.8.x, by:
>
> * Adding appropriate patches to gcc 4.7 and gcc 4.8 in the internal
> toolchain backend.
>
> * Allowing external toolchains to indicate whether they are affected
> by the bug. For now, one toolchain known to be affected is marked
> as such, the other toolchains will have to be tested progressively.
>
> * Making the lttng-tools depend on toolchains not affected by the
> bug.
>
> Thomas Petazzoni (4):
> gcc: add fix for PR 58595 to gcc 4.8.2
> gcc: add fix for PR 58595 to gcc 4.7.3
> toolchain: add option to declare toolchains affected by gcc PR 58595
> lttng-tools: mark as affected by gcc bug 58595
Applied.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-04-14 20:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-13 19:58 [Buildroot] [PATCH 0/4] Fix lttng-tools build issue Thomas Petazzoni
2014-04-13 19:58 ` [Buildroot] [PATCH 1/4] gcc: add fix for PR 58595 to gcc 4.8.2 Thomas Petazzoni
2014-04-13 19:58 ` [Buildroot] [PATCH 2/4] gcc: add fix for PR 58595 to gcc 4.7.3 Thomas Petazzoni
2014-04-13 19:58 ` [Buildroot] [PATCH 3/4] toolchain: add option to declare toolchains affected by gcc PR 58595 Thomas Petazzoni
2014-04-13 19:58 ` [Buildroot] [PATCH 4/4] lttng-tools: mark as affected by gcc bug 58595 Thomas Petazzoni
2014-04-14 20:42 ` Thomas Petazzoni [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=20140414224220.68a5b2fb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox