[opensuse-arm] An update about fixed and packages being worked on.
Hi all, MozillaFireFox 10 will be fixed for ARM with the option --disable-neon. I've already tested this patch for MozillaFirefox 9.0 and I'm building MozillaFirefox 9.0.1 in home:worldcitizen:armv7l . What way would be best to communicate so no double work will be done. An overview of who is fixing what. I've also created a bug report for webkit, as this is not an ARM only bug. https://bugs.webkit.org/show_bug.cgi?id=76798 Regards, Joop. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Dienstag, 31. Januar 2012, 14:08:43 schrieb Joop Boonen:
Hi all,
MozillaFireFox 10 will be fixed for ARM with the option --disable-neon.
k, I have added this for now (even though it is only a workaround, since firefox should check this at runtime).
I've already tested this patch for MozillaFirefox 9.0 and I'm building MozillaFirefox 9.0.1 in home:worldcitizen:armv7l .
What way would be best to communicate so no double work will be done. An overview of who is fixing what.
I've also created a bug report for webkit, as this is not an ARM only bug. https://bugs.webkit.org/show_bug.cgi?id=76798
good :)
Regards,
Joop. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Tue, January 31, 2012 2:38 pm, Adrian Schröter wrote:
Am Dienstag, 31. Januar 2012, 14:08:43 schrieb Joop Boonen:
Hi all,
MozillaFireFox 10 will be fixed for ARM with the option --disable-neon.
k, I have added this for now (even though it is only a workaround, since firefox should check this at runtime).
I agree it's a workaround. Patch: mozilla-disable-neon-option.patch is also needed. The package can be found here: home:worldcitizen:armv7l MozillaFirefox
I've already tested this patch for MozillaFirefox 9.0 and I'm building MozillaFirefox 9.0.1 in home:worldcitizen:armv7l .
What way would be best to communicate so no double work will be done. An overview of who is fixing what.
I've also created a bug report for webkit, as this is not an ARM only bug. https://bugs.webkit.org/show_bug.cgi?id=76798
good :)
I've has a successful build of webkit 1.7.3 before with 2GB of swap and an adapted /usr/lib/build/build file. --- /usr/lib/build/build.orig 2000-01-01 01:16:30.000000000 +0100 +++ /usr/lib/build/build 2000-01-01 01:16:45.000000000 +0100 @@ -428,7 +428,8 @@ local mem while read mem; do case "$mem" in - MemTotal:*) +# MemTotal:*) + SwapTotal:*) set -- $mem eval "mem=\$(($2/3*4))" ulimit -v $mem I couldn't build webkit 1.7.4 anymore.
Regards,
Joop. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Regards, Joop. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Dienstag, 31. Januar 2012, 22:19:34 schrieb Joop Boonen:
On Tue, January 31, 2012 2:38 pm, Adrian Schröter wrote:
Am Dienstag, 31. Januar 2012, 14:08:43 schrieb Joop Boonen:
Hi all,
MozillaFireFox 10 will be fixed for ARM with the option --disable-neon.
k, I have added this for now (even though it is only a workaround, since firefox should check this at runtime).
I agree it's a workaround. Patch: mozilla-disable-neon-option.patch is also needed. The package can be found here: home:worldcitizen:armv7l MozillaFirefox
k, merged that.
I've already tested this patch for MozillaFirefox 9.0 and I'm building MozillaFirefox 9.0.1 in home:worldcitizen:armv7l .
What way would be best to communicate so no double work will be done. An overview of who is fixing what.
I've also created a bug report for webkit, as this is not an ARM only bug. https://bugs.webkit.org/show_bug.cgi?id=76798
good :)
I've has a successful build of webkit 1.7.3 before with 2GB of swap and an adapted /usr/lib/build/build file.
current code is now adding mem and swap.
--- /usr/lib/build/build.orig 2000-01-01 01:16:30.000000000 +0100 +++ /usr/lib/build/build 2000-01-01 01:16:45.000000000 +0100 @@ -428,7 +428,8 @@ local mem while read mem; do case "$mem" in - MemTotal:*) +# MemTotal:*) + SwapTotal:*) set -- $mem eval "mem=\$(($2/3*4))" ulimit -v $mem
I couldn't build webkit 1.7.4 anymore.
Regards,
Joop.
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Regards,
Joop.
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Tuesday 31 January 2012, Joop Boonen wrote:
MozillaFireFox 10 will be fixed for ARM with the option --disable-neon. I've already tested this patch for MozillaFirefox 9.0 and I'm building MozillaFirefox 9.0.1 in home:worldcitizen:armv7l .
Hi Joop, thanks, but this patch did not end up upstream ? I think the problem you tried to fix was a duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=724615 while fixing the build for xulrunner 10 I noticed that this one liner solves all issues, so I included that one instead and submitted it to the devel project. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (3)
-
Adrian Schröter -
Dirk Müller -
Joop Boonen