From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@buildroot.org
Subject: [Buildroot] [PATCH v2] package/mpg123: fix linking error
Date: Tue, 8 Aug 2023 08:54:49 +0200 [thread overview]
Message-ID: <ZNHmuZ6+nRwp71r/@waldemar-brodkorb.de> (raw)
This was introduced since commit f8af24707b196eb64121d29a829fc31b5506409c.
Patch was provided by upstream:
https://sourceforge.net/p/mpg123/bugs/353/
Fixes:
- http://autobuild.buildroot.net/results/74e/74e1522cc9328c98186ca730eeb7ce0cb5fbbcb5
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
---
v1 -> v2:
- add a specific autobuild failure
- use Fixes: for link to autobuilder
- add a reference to a buildroot commit, when the problem was
introduced
---
package/mpg123/0001-mpg123-buildfix.patch | 24 +++++++++++++++++++++++
1 file changed, 24 insertions(+)
create mode 100644 package/mpg123/0001-mpg123-buildfix.patch
diff --git a/package/mpg123/0001-mpg123-buildfix.patch b/package/mpg123/0001-mpg123-buildfix.patch
new file mode 100644
index 0000000000..cc731ea967
--- /dev/null
+++ b/package/mpg123/0001-mpg123-buildfix.patch
@@ -0,0 +1,24 @@
+Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
+Upstream: https://sourceforge.net/p/mpg123/bugs/353/
+
+diff -Nur mpg123-1.31.3.orig/src/libmpg123/getcpuflags.h mpg123-1.31.3/src/libmpg123/getcpuflags.h
+--- mpg123-1.31.3.orig/src/libmpg123/getcpuflags.h 2023-03-15 09:02:58.000000000 +0100
++++ mpg123-1.31.3/src/libmpg123/getcpuflags.h 2023-08-07 15:57:19.444106173 +0200
+@@ -44,6 +44,8 @@
+
+ unsigned int getcpuflags(struct cpuflags* cf);
+
++#if ((defined OPT_X86) || (defined OPT_X86_64) || (defined OPT_NEON) || (defined OPT_NEON64)) && (defined OPT_MULTI)
++
+ #ifdef WANT_GETCPUFLAGS
+ #include <string.h>
+ // Wrapper needed for ignorant clang memory sanitizer that chokes
+@@ -55,8 +57,6 @@
+ }
+ #endif
+
+-#if ((defined OPT_X86) || (defined OPT_X86_64) || (defined OPT_NEON) || (defined OPT_NEON64)) && (defined OPT_MULTI)
+-
+ // We really evaluate the CPU flags.
+ #define OPT_CPU_FLAGS
+
--
2.39.2
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-08-08 6:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 6:54 Waldemar Brodkorb [this message]
2023-08-22 21:40 ` [Buildroot] [PATCH v2] package/mpg123: fix linking error Thomas Petazzoni via buildroot
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=ZNHmuZ6+nRwp71r/@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox