From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org
Subject: [Buildroot] [git commit branch/2022.08.x] package/sox: work around gcc bug 68485
Date: Sun, 18 Sep 2022 23:11:05 +0200 [thread overview]
Message-ID: <20220918211221.30FC1854C8@busybox.osuosl.org> (raw)
commit: https://git.buildroot.net/buildroot/commit/?id=5913c02656220b6c79207f03ebc7e7c50a8f073d
branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/2022.08.x
sox is impacted by the microblaze-specific gcc bug #68485 [0], which is
still unfixed as of gcc 12.x.
As for all other impacted packages, force no optimisation when using a
toolchain riddled with that bug.
Fixes:
http://autobuild.buildroot.net/results/ac4/ac4fbd55529ac7b4e635a11766f842cd25a833a1/
[0] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68485
Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
(cherry picked from commit dd8a8cfa9a584934bb2707c197c43073d6c03436)
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
---
package/sox/sox.mk | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/package/sox/sox.mk b/package/sox/sox.mk
index 1896437ad4..d0329bf50d 100644
--- a/package/sox/sox.mk
+++ b/package/sox/sox.mk
@@ -26,6 +26,14 @@ SOX_CONF_OPTS = \
--with-distro="Buildroot" \
--disable-stack-protector
+SOX_CFLAGS = $(TARGET_CFLAGS)
+
+ifeq ($(BR2_TOOLCHAIN_HAS_GCC_BUG_68485),y)
+SOX_CFLAGS += -O0
+endif
+
+SOX_CONF_ENV += CFLAGS="$(SOX_CFLAGS)"
+
ifeq ($(BR2_PACKAGE_ALSA_LIB_PCM),y)
SOX_DEPENDENCIES += alsa-lib
SOX_CONF_OPTS += --enable-alsa
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
reply other threads:[~2022-09-18 21:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220918211221.30FC1854C8@busybox.osuosl.org \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
/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.