RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 798880 - Build xulrunner with enabled WebM there.
Summary: Build xulrunner with enabled WebM there.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: xulrunner
Version: 6.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Martin Stransky
QA Contact: Desktop QE
URL:
Whiteboard:
: 808145 (view as bug list)
Depends On: 812828
Blocks: 782183 840699
TreeView+ depends on / blocked
 
Reported: 2012-03-01 07:31 UTC by Martin Stransky
Modified: 2018-11-28 20:56 UTC (History)
8 users (show)

Fixed In Version: RHSA-2012:1088
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 812828 (view as bug list)
Environment:
Last Closed: 2012-08-03 10:50:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
old nasm fix/workaround. (387 bytes, patch)
2012-05-03 07:03 UTC, Jan Kratochvil
no flags Details | Diff

Description Martin Stransky 2012-03-01 07:31:05 UTC
Description of problem:

Build xulrunner with system libvpx which enables WebM there.

Comment 1 RHEL Program Management 2012-03-01 07:49:26 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has 
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed 
products. This request is not yet committed for inclusion in an Update release.

Comment 2 Martin Stransky 2012-03-05 09:48:57 UTC
Unfortunately we need libvpx 0.9.7 for it (at least) but the recent RHEL6 package is 0.9.0.

Comment 3 Martin Stransky 2012-04-16 11:13:07 UTC
We have to fix Bug 812828 first.

Comment 4 Jonathan Blandford 2012-05-01 14:54:07 UTC
In the interim, can we build firefox with an internal copy of libvpx, Martin?

Comment 6 Martin Stransky 2012-05-02 06:51:04 UTC
(In reply to comment #4)
> In the interim, can we build firefox with an internal copy of libvpx, Martin?

Yes, we can build firefox an internal copy of libvpx, but without updated system yasm we'd need to bundle the new yasm package with xulrunner. Do we want to do so?

Comment 7 Jan Kratochvil 2012-05-02 17:01:34 UTC
xulrunner-10.0.4-1.el6 ./mozilla-esr10/media/libvpx/README_MOZILLA states:
Using the v0.9.5 release pulled from
http://webm.googlecode.com/files/libvpx-v0.9.5.zip

and libvpx-v0.9.5.zip already contains my last commit
7be093ea4d50c8d38438f88cb9fa817c1c9de8dd
and its libvpx-v0.9.5/configure really supports:
  --as={yasm|nasm|auto}           use specified assembler [auto, yasm preferred]

Just the libvpx configure options are removed in the Mozilla bundle but all the patches for nasm support are there.  Upgrade to libvpx-1.0.0 will not change anything wrt the nasm support for libvpx.

Comment 8 Jan Kratochvil 2012-05-03 07:03:20 UTC
Created attachment 581786 [details]
old nasm fix/workaround.

The problem with old nasm was just that it automatically did not promote section alignment if an alignment was used in that section.

This patch is not optimal as it aligns all the libvpx .o files data rodata sections and not just those containing the aligned variables but it should not matter.

I have checked all "align 16" statements are present only after SECTION_RODATA.

I did not test the output myself now.

QA:
These ELF symbols (nm) must be aligned to 16 bytes:

x_s1sqr2 x_c1sqr2less1 fours Blur rd42 x_s1sqr2 x_c1sqr2less1 fours tfe t80 t1s t3 t4 ones s27 s18 s9 s63 rd vp8_six_tap_mmx vp8_bilinear_filters_mmx fours x_s1sqr2 x_c1sqr2less1 tfe t80 t1s t3 t4 ones s9 s63 dc_1024 dc_00001111 rd shuf1b shuf2bfrom1 shuf3bfrom1 rd k0_k5 vp8_bilinear_filters_ssse3 x_s1sqr2 x_c1sqr2less1 fours t80 c1 cn1 cd1 cd3 xmm_bi_rd vp8_bilinear_filters_ssse3 inv_zig_zag _5352_2217 _2217_neg5352 _mult_add _cmp_mask _cmp_mask8x4 _mult_sub _7 _7w _14500 _7500 _12000 _51000 mmx_bi_rd zz_shuf xmm_bi_rd vp8_bilinear_filters_sse2 _const_3w _const_top_bit _const_16w zig_zag1d

Comment 12 Martin Stransky 2012-06-12 07:16:59 UTC
Patch is ready, we can ship it in next update.

Comment 16 RHEL Program Management 2012-06-20 15:13:57 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has 
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed 
products. This request is not yet committed for inclusion in an Update release.

Comment 18 Jonathan Blandford 2012-07-02 18:26:27 UTC
*** Bug 808145 has been marked as a duplicate of this bug. ***

Comment 19 Martin Stransky 2012-08-03 10:50:34 UTC
Already fixed in Firefox 10.0.6. Looks like we forget to add the bug to the advisory.


Note You need to log in before you can comment on or make changes to this bug.