Closed Bug 792988 Opened 7 years ago Closed 7 years ago

Otoro builds broken: "media/omx-plugin/OmxPlugin.cpp:605: error: 'OMX_QCOM_COLOR_FormatYVU420SemiPlanar' was not declared in this scope"

Categories

(Core :: Audio/Video, defect, critical)

ARM
Gonk (Firefox OS)
defect
Not set
critical

Tracking

()

RESOLVED FIXED
mozilla18
blocking-basecamp +

People

(Reporter: cjones, Assigned: cjones)

References

Details

Attachments

(1 file)

http://hg.mozilla.org/integration/mozilla-inbound/rev/4be1a01f58f3#l1.114 removed these local defines of constants.

This isn't tbpl builds, which is *highly* disturbing.  Does this code depend on device-specific environment?  That's something we need to fix; maybe it's what the local constants were trying to achieve.
Severity: normal → critical
blocking-basecamp: --- → +
We need to get the build bustage off of inbound *ASAP*, but after that we need to make sure this kind of problem doesn't happen again.  Likely a problem with the b2g build config.
Assignee: nobody → jones.chris.g
Attachment #663158 - Flags: review?(cpeterson)
Attachment #663158 - Flags: review?(cpeterson) → review+
The omx plugin isn't enabled on tbpl. It has to be explicitly turned on and the mozconfig doesn't turn it on. I also don't know if our b2g toolchain package currently supports OMX.
https://hg.mozilla.org/mozilla-central/rev/6d8a6c8f06cc
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla18
Depends on: 793229
You need to log in before you can comment on or make changes to this bug.