From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] gcc/libmudflap: unavailable for gcc >= 4.9
Date: Tue, 7 Jun 2016 23:44:40 +0200 [thread overview]
Message-ID: <20160607234440.678e2e68@free-electrons.com> (raw)
In-Reply-To: <1465058756-9612-1-git-send-email-bernd.kuhls@t-online.de>
Hello,
On Sat, 4 Jun 2016 18:45:56 +0200, Bernd Kuhls wrote:
> Rework gcc dependency for mudflap as suggested by Arnout and Peter:
> http://article.gmane.org/gmane.comp.lib.uclibc.buildroot/149813
>
> libmudflap was removed in gcc 4.9:
> https://gcc.gnu.org/wiki/Mudflap_Pointer_Debugging
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/gcc/Config.in.host | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
Applied to master, thanks. We will be able to remove mudflap support
when gcc 4.8 gets deprecated.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-06-07 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 16:45 [Buildroot] [PATCH 1/1] gcc/libmudflap: unavailable for gcc >= 4.9 Bernd Kuhls
2016-06-07 21:44 ` 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=20160607234440.678e2e68@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