This bug was fixed in the package chromium-browser -
10.0.648.204~r79063-0ubuntu1
---
chromium-browser (10.0.648.204~r79063-0ubuntu1) natty; urgency=high
* New upstream minor release from the Stable Channel (LP: #742118)
This release fixes the following security issues:
+ We
So the fix is to set arm_fpu=vfpv3-d16 at build time.
Committed in the branch, I will land it downward in the channels and in
the next stable update
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
** Changed in: chromium-browser (Ubuntu)
Status: New => Fix Comm
http://code.google.com/p/chromium/issues/detail?id=38957 seems
relevant. See #c8 in that thread.
I think it's definitely not a compiler error but more of a package
configuration issue. Either ubuntu had a local patch to change this to
vfpv3-d16 or chromium did and someone dropped this patch ?
ch
Well the smoking gun in the source seems to be:
build/common.gypi:
# Set ARM fpu compilation flags (only meaningful if armv7==1 and
# arm_neon==0).
'arm_fpu%': 'vfpv3',
and the build logs to show arm_neon=0 and armv7=1- it's not clear to
me how the .gypi files work, but that needs
** Tags added: arm-porting-queue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/735877
Title:
Illegal instruction in chromium on startup on armel
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
Just in case - the AC100 is vfpv3-d16 hardware only.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/735877
Title:
Illegal instruction in chromium on startup on armel
--
ubuntu-bugs mailing list
ubu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/735877
Title:
Illegal instruction in chromium on startup on armel
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mai
