6.x doesn't build with arm_neon anymore
Bug #641158 reported by
Loïc Minier
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Chromium Browser |
Unknown
|
Unknown
|
|||
| chromium-codecs-ffmpeg (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Binary package hint: chromium-browser
Hi
Since moving 6.x, chromium-browser doesn't build with arm_neon anymore (fails in ffmpeg), so it was disabled. http://
It would be good to investigate how the builtin ffmpeg copy can be fixed; I personally believe upstream ffmpeg works fine when built with NEON support, so I suspect it's just a matter of identifying the borken divergence.
Cheers,
| tags: | added: armel neon |
Revision history for this message
| Fabien Tassin (fta) wrote | #1 |
| affects: | chromium-browser (Ubuntu) → chromium-codecs-ffmpeg (Ubuntu) |
| Changed in chromium-codecs-ffmpeg (Ubuntu): | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| tags: | added: arm-porting-queue |
Revision history for this message
| Jani Monoses (jani) wrote | #2 |
| Changed in chromium-codecs-ffmpeg (Ubuntu): | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
in the past, there was no arm_neon knob in the chromium build system.
it landed with this patch a while ago: http://
but it took time to reach the stable branch (ffmpeg 0.5->0.6 transition at the same time as the chromium 5->6 transition).
I didn't notice earlier because i don't have access to any arm machine so none of my zillions daily/dev/
So to be able to unblock the security updates, i had to disable that arm_neon knob.
as for using the system ffmpeg, it would first need to be multi-threaded but the ubuntu trend for browsers is to move back to the in-source libs (started with firefox a while ago).