From: Max Krummenacher <max.oss.09@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: gary@mlbassoc.com
Subject: [meta-browser][PATCH 3/8] firefox: prevent SIGILL crash with arm build
Date: Sun, 16 Aug 2015 21:40:18 +0200 [thread overview]
Message-ID: <1439754023-13290-4-git-send-email-max.oss.09@gmail.com> (raw)
In-Reply-To: <1439754023-13290-1-git-send-email-max.oss.09@gmail.com>
Firefox crashes with a SIGILL signal during startup.
Signed-off-by: Max Krummenacher <max.oss.09@gmail.com>
---
recipes-mozilla/firefox/firefox/alignment.patch | 17 +++++++++++++++++
recipes-mozilla/firefox/firefox_10.0.11esr.bb | 3 ++-
2 files changed, 19 insertions(+), 1 deletion(-)
create mode 100644 recipes-mozilla/firefox/firefox/alignment.patch
diff --git a/recipes-mozilla/firefox/firefox/alignment.patch b/recipes-mozilla/firefox/firefox/alignment.patch
new file mode 100644
index 0000000..f5d5b7c
--- /dev/null
+++ b/recipes-mozilla/firefox/firefox/alignment.patch
@@ -0,0 +1,17 @@
+In some setups firefox crashes because of wrongly aligned variables
+Observed on a ARM Cortex-A9 target.
+
+Upstream-Status: Pending
+
+Signed-off-by: Max Krummenacher <max.oss.09 at gmail.com>
+--- mozilla-release/ipc/ipdl/ipdl/cxx/cgen.py~ 2012-07-29 11:14:45.000000000 +0200
++++ mozilla-release/ipc/ipdl/ipdl/cxx/cgen.py 2012-07-29 11:13:36.000000000 +0200
+@@ -107,7 +107,7 @@
+ self.println(';')
+ self.dedent()
+
+- self.printdent('}')
++ self.printdent('} __attribute__ ((aligned (__BIGGEST_ALIGNMENT__)))')
+
+
+ def visitTypedef(self, td):
diff --git a/recipes-mozilla/firefox/firefox_10.0.11esr.bb b/recipes-mozilla/firefox/firefox_10.0.11esr.bb
index e07555b..cb368d0 100644
--- a/recipes-mozilla/firefox/firefox_10.0.11esr.bb
+++ b/recipes-mozilla/firefox/firefox_10.0.11esr.bb
@@ -75,7 +75,8 @@ SRC_URI = "https://archive.mozilla.org/pub/firefox/releases/${PV}/source/firefox
file://powerpc_va_list.patch \
file://freetype-2.5.patch \
file://x86_64-fix.patch \
- file://vendor.js"
+ file://vendor.js \
+ file://alignment.patch"
SRC_URI[archive.md5sum] = "2f0e3a1dd7480e03f374c0121b4155e2"
SRC_URI[archive.sha256sum] = "94b4d5a339d97dc56fd349f93407c3af4f408a4a8409a64e3680d564d37594f8"
--
1.8.4.5
next prev parent reply other threads:[~2015-08-16 19:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-16 19:40 [meta-browser][PATCH 0/8] firefox: fixes and update to 10.0.12esr Max Krummenacher
2015-08-16 19:40 ` [meta-browser][PATCH 1/8] firefox: Update download server Max Krummenacher
2015-08-16 19:40 ` [meta-browser][PATCH 2/8] firefox-l10n: " Max Krummenacher
2015-08-16 19:40 ` Max Krummenacher [this message]
2015-08-16 19:40 ` [meta-browser][PATCH 4/8] firefox: prevent SIGILL crash #2 with arm build Max Krummenacher
2015-08-16 19:40 ` [meta-browser][PATCH 5/8] firefox: stop using variable for local files Max Krummenacher
2015-08-16 19:40 ` [meta-browser][PATCH 6/8] mozilla.bbclass: do out of tree build Max Krummenacher
2015-08-16 19:40 ` [meta-browser][PATCH 7/8] firefox: Update to 10.0.12esr Max Krummenacher
2015-08-16 19:40 ` [meta-browser][PATCH 8/8] firefox-l10n: Update all languages for 10.0.12esr release Max Krummenacher
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=1439754023-13290-4-git-send-email-max.oss.09@gmail.com \
--to=max.oss.09@gmail.com \
--cc=gary@mlbassoc.com \
--cc=openembedded-devel@lists.openembedded.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