Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Asaf Kahlon <asafka7@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/collectd: work around gcc bug 68485
Date: Mon, 26 Sep 2022 14:09:06 +0200	[thread overview]
Message-ID: <20220926140906.6167d2e3@windsurf> (raw)
In-Reply-To: <20220924230826.283565-1-giulio.benetti@benettiengineering.com>

On Sun, 25 Sep 2022 01:08:26 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:

> collectd is impacted by the microblaze-specific gcc bug #68485 [0].
> 
> As for all other impacted packages, force no optimisation when using a
> toolchain riddled with that bug.
> 
> Fixes:
>    http://autobuild.buildroot.net/results/6a8/6a87bbe17e6f606a97097800dc484a7b17bffa7d/
> 
> [0] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68485
> 
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> ---
>  package/collectd/collectd.mk | 8 ++++++++
>  1 file changed, 8 insertions(+)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-09-26 12:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-24 23:08 [Buildroot] [PATCH] package/collectd: work around gcc bug 68485 Giulio Benetti
2022-09-26 12:09 ` Thomas Petazzoni [this message]
2022-10-12 15:44 ` Peter Korsgaard

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=20220926140906.6167d2e3@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=asafka7@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    /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