From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libmpeg2: fix sparc32 build
Date: Thu, 27 Apr 2017 07:36:09 +0200 [thread overview]
Message-ID: <20170427053609.GA20301@waldemar-brodkorb.de> (raw)
The output detection recognized wrong target output, because
sparcv9 optimization flags used for sparcv8 build.
Fixes:
http://autobuild.buildroot.net/results/1b3158b03f7eaf5afb5a4dab9526091888f6c9b8
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
---
package/libmpeg2/0004-fix-sparc.patch | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
create mode 100644 package/libmpeg2/0004-fix-sparc.patch
diff --git a/package/libmpeg2/0004-fix-sparc.patch b/package/libmpeg2/0004-fix-sparc.patch
new file mode 100644
index 0000000..d876b66
--- /dev/null
+++ b/package/libmpeg2/0004-fix-sparc.patch
@@ -0,0 +1,16 @@
+Do not use sparcv9 optimization flags for sparcv8 builds
+
+Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
+
+diff -Nur libmpeg2-0.5.1.orig/configure.ac libmpeg2-0.5.1/configure.ac
+--- libmpeg2-0.5.1.orig/configure.ac 2008-07-18 16:30:17.000000000 +0200
++++ libmpeg2-0.5.1/configure.ac 2017-04-26 21:09:15.780838339 +0200
+@@ -95,7 +95,7 @@
+ break
+ fi
+ done;;
+- sparc-* | sparc64-*)
++ sparc64-*)
+ AC_DEFINE([ARCH_SPARC],,[sparc architecture])
+ TRY_CFLAGS="$OPT_CFLAGS -mcpu=ultrasparc -mvis"
+ AC_TRY_CFLAGS([$TRY_CFLAGS $CFLAGS],[OPT_CFLAGS="$TRY_CFLAGS"]);;
--
2.1.4
next reply other threads:[~2017-04-27 5:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 5:36 Waldemar Brodkorb [this message]
2017-04-27 8:18 ` [Buildroot] [PATCH] libmpeg2: fix sparc32 build Peter Korsgaard
2017-04-28 0:32 ` Waldemar Brodkorb
2017-04-27 8:26 ` Thomas Petazzoni
2017-04-27 9:15 ` Peter Korsgaard
2017-04-27 9:22 ` Thomas Petazzoni
2017-04-27 19:30 ` Arnout Vandecappelle
2017-04-27 20:04 ` 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=20170427053609.GA20301@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--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