17:18:44 hello 17:18:45 i'm about to build Seamonkey 2.53.10. It stops (like the older versions 2.53.3 again) due to an error 17:18:47 struct vpx_svc_ref_frame_config has no member named frame_flags 17:18:48 in the webrtc files. See 17:18:50 https://pastebin.mozilla.org/4un0fDcy 17:18:51 With 2.53.3, i used the option disable-webrtc to avoid the problem. Is the problem known to somebody here? 17:19:33 mlh85386: sounds like an obsolete/too new (?) libvpx header 17:19:46 have never compiled SeaMonkey, but I can recognize the symbol 17:20:20 https://bugs.gentoo.org/712264 17:21:17 tomman: thanks I'll have a look on the gentoo record 17:55:21 mlh85386: would have been better if you pointed this out when it first occurred, but we can probably figure it out. rporting it against 2.53.10 but saying it has failed for you since 2.53.3 is less useful at this point than if you reported it sooner to when the issue began 17:59:04 wg9s: I tried compiling 2.53.3 recently, a couple of days ago. So the problem was new to me too. 17:59:24 well that is better 17:59:57 spo when it failed you went back to find last working build that is better than what you described 18:01:38 tomman: it is really a version problem. libvpx version 1.9.0 is installed locally, according to the bug report on gentoo <= 1.8.0 would be needed 18:01:56 i thought you meant i am just reporting this but it has not worked since and earlier version but did not bother to ell you. My response was based on my understanding this as being the second scenario. 18:02:11 just remove the system-libvpx statement from the mozconfig. 18:02:32 ah so having a version of libvpx insalled locally might require later code not in SeaMonkey 2.53? 18:03:01 mlh85386: so "too new" is it 18:03:09 typical with multimedia stuff, like ffmpeg and friends 18:03:18 hence why I recognized the symbols 18:04:43 Thanks: removing option with-system-libvpx in mozconfig is what I just did 18:07:04 i have no -with-system- anything in my mozconfig and all works just fine for me. 18:10:50 wg9s: Probably it's better to have not. My fault to try it with some of them. To use components already installed 18:10:58 if it does not build with -wit-system- then file aboug on your distro 18:33:31 I try to sync all this stuff with mozilla-central as fast as possible but it is a loosing game with so few devs around. So best to either remove --with-system or just help with porting the stuff. There are naturally adavnatges with using the system libriries but unfortunately they change interfaces much too frequently these days. 18:42:11 frg_away: Nevertheless: Thanks for your work and your support 18:43:01 I try ... :) 19:05:11 FFmpeg is a sample case of pure madness, as they don't really believe in a stable API 19:05:26 every minor release breaks something 19:05:50 and until a few years ago, their solution was "don't use point releases, always target git-HEAD" 19:06:24 at least they now do some sort of LTS with every minor release 20:52:02 is GitHub acting all weird again? 20:52:14 all I'm getting are HTTP 500 error pages here since a while 20:53:57 https://www.githubstatus.com/ yup, it's (mostly) down 20:55:52 https://news.ycombinator.com/item?id=29363169 and it's not me only 20:56:11 remind me why trusting a centralized sourcecode repo was so awesome for the Internet? 23:06:37 tomman seems worse since Microsoft took over 23:06:55 apparently GiggityHub is back now 23:07:11 still... man, remind me why centralization of EVERYTHING is good.... 23:07:13 oh wait 23:07:16 it isn't :/ 23:07:46 saw tons of people screaming in agony because their build workflows can't work without GitHub... or the Internet in general 23:08:19 it is like people forgot that offline/manual installation of dependencies was a thing 23:17:49 tomman: if it were not a saturday mozilla trees would be closed becuase i don;t think an autoland build will work if github is ddown