seamonkey-2.53.1 fails to build with libvpx-1.8.2: In file included from /tmp/portage/www-client/seamonkey-2.53.1/work/seamonkey-2.53.1/seamonk/media/webrtc/trunk/webrtc/modules/video_coding/webrtc_vp9_gn/Unified_cpp_webrtc_vp9_gn0.cpp:20: /tmp/portage/www-client/seamonkey-2.53.1/work/seamonkey-2.53.1/mozilla/media/webrtc/trunk/webrtc/modules/video_coding/codecs/vp9/vp9_impl.cc: In member function vpx_svc_ref_frame_config webrtc::VP9EncoderImpl::GenerateRefsAndFlags(const webrtc::VP9EncoderImpl::SuperFrameRefSettings&)': /tmp/portage/www-client/seamonkey-2.53.1/work/seamonkey-2.53.1/mozilla/media/webrtc/trunk/webrtc/modules/video_coding/codecs/vp9/vp9_impl.cc:858:17: error: 'struct vpx_svc_ref_frame_config' has no member named 'frame_flags' 858 | sf_conf.frame_flags[layer_idx] = layer_flags; | ^~~~~~~~~~~ sf_conf is of type vpx_svc_ref_frame_config; the definition of this structure changed between libvpx-1.7.0 and libvpx-1.8.2, the latter of which does not have a frame_flags field. Building with libvpx-1.7.0-r1 succeeds.
I seem to be getting the same here. Started a couple weeks ago. In file included from /var/tmp/portage/www-client/seamonkey-2.53.1/work/seamonkey-2.53.1/seamonk/media/webrtc/trunk/webrtc/modules/video_coding/webrtc_vp9_gn/Unified_cpp_webrtc_vp9_gn0.cpp:20: /var/tmp/portage/www-client/seamonkey-2.53.1/work/seamonkey-2.53.1/mozilla/media/webrtc/trunk/webrtc/modules/video_coding/codecs/vp9/vp9_impl.cc: In member function 'vpx_svc_ref_frame_config webrtc::VP9EncoderImpl::GenerateRefsAndFlags(const webrtc::VP9EncoderImpl::SuperFrameRefSettings&)': /var/tmp/portage/www-client/seamonkey-2.53.1/work/seamonkey-2.53.1/mozilla/media/webrtc/trunk/webrtc/modules/video_coding/codecs/vp9/vp9_impl.cc:858:17: error: 'struct vpx_svc_ref_frame_config' has no member named 'frame_flags' 858 | sf_conf.frame_flags[layer_idx] = layer_flags; | ^~~~~~~~~~~ /var/tmp/portage/www-client/seamonkey-2.53.1/work/seamonkey-2.53.1/mozilla/media/webrtc/trunk/webrtc/modules/video_coding/codecs/vp9/vp9_impl.cc: In constructor 'webrtc::VP9DecoderImpl::VP9DecoderImpl()': /var/tmp/portage/www-client/seamonkey-2.53.1/work/seamonkey-2.53.1/mozilla/media/webrtc/trunk/webrtc/modules/video_coding/codecs/vp9/vp9_impl.cc:893:36: warning: 'void* memset(void*, int, size_t)' clearing an object of non-trivial type 'class webrtc::VideoCodec'; use assignment or value-initialization instead [-Wclass-memaccess] 893 | memset(&codec_, 0, sizeof(codec_)); If more info is needed, let me know. Going to try solution listed in previous comment.
FYI, apparently there's no upstream bug. I guess they should be put in the loop, right?
(In reply to sphakka from comment #2) > FYI, apparently there's no upstream bug. I guess they should be put in the > loop, right? Maybe a dev will know how to do that. I couldn't downgrade libvpx since Firefox wants the new one. Emerge puked on my keyboard about that. I guess I'm stuck with the older version of Seamonkey until either a new release that works or this is fixed.
@dale, as for Firefox, I just downgraded it yesterday with libvpx, etc. with no issue (a part from biblical compile times). Just be sure to have a backup of your older FF68 profile because it's not compatible with a newer FF7x -- FF should refuse to run on it, anyway. Otherwise you have a Firefox bug...
(In reply to Dale from comment #3) > (In reply to sphakka from comment #2) > > FYI, apparently there's no upstream bug. I guess they should be put in the > > loop, right? > > Maybe a dev will know how to do that. I couldn't downgrade libvpx since > Firefox wants the new one. Emerge puked on my keyboard about that. I guess > I'm stuck with the older version of Seamonkey until either a new release > that works or this is fixed. simply disable the system-libvpx useflag and you will be able to keep libvpx-1.7
(In reply to sphakka from comment #2) > FYI, apparently there's no upstream bug. I guess they should be put in the > loop, right? Upsteram far as mozilla goes is already fixed. Problem is seamonkey is so far behind it is not gonna be an easy patch to backport.
By the way, same here with seamonkey-2.53.2. Going back to bundled libvpx for this version.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d26bb1194732de2120fe1fd4e50f7b997b61eadc commit d26bb1194732de2120fe1fd4e50f7b997b61eadc Author: Lars Wendler <polynomial-c@gentoo.org> AuthorDate: 2020-08-15 10:24:56 +0000 Commit: Lars Wendler <polynomial-c@gentoo.org> CommitDate: 2020-08-15 10:25:21 +0000 www-client/seamonkey: Fixed build with USE="system-libvpx" Closes: https://bugs.gentoo.org/712264 Package-Manager: Portage-3.0.2, Repoman-2.3.23 Signed-off-by: Lars Wendler <polynomial-c@gentoo.org> www-client/seamonkey/Manifest | 1 + www-client/seamonkey/seamonkey-2.53.3.ebuild | 4 +++- 2 files changed, 4 insertions(+), 1 deletion(-)