Bug 791513 updated yasm to 1.2 back in 2012. mozilla-build was updated to yasm 1.3 in bug 1113450. However, the build boxes still use yasm 1.1 As part of bug 1214462, we are integrating some parts of FFmpeg which requires yasm >= 1.2 Yasm 1.1 can't do AVX2 which is used by the VP9 decoder.

Chris - who can fix this issue?

On Windows, Mark can let you know what's involved.

Currently it would involve an adjustment to the base image for the try builders, and a GPO to catch the non-try builders. As well as include into my non-try builders testing. Ultimately it will should be rolled into Puppet once we get to automating the build AMI creation.

(In reply to Mark Cornmesser [:markco] from comment #3) > Ultimately it will should be rolled into Puppet once we get to automating > the build AMI creation. What is the ETA for that?

mozilla-central has yasm code in libvpx, spidermonkey, skia, cairo, nss, libjpeg, and webrtc. We need to give those teams a heads-up when we update yasm.

(In reply to Chris Peterson [:cpeterson] from comment #5) > mozilla-central has yasm code in libvpx, spidermonkey, skia, cairo, nss, > libjpeg, and webrtc. We need to give those teams a heads-up when we update > yasm. The current mozilla-build already has 1.3 ; so anyone building locally would be using 1.3 already. It's also the default on mac or any > 4 years old linux distribution.

(In reply to Anthony Jones (:kentuckyfriedtakahe, :k17e) from comment #4) > (In reply to Mark Cornmesser [:markco] from comment #3) > > Ultimately it will should be rolled into Puppet once we get to automating > > the build AMI creation. > > What is the ETA for that? Puppet specifically will need to be after we have 2008 non-try builds working in AWS. However, without Puppet I can get it deployed this week.

I am rolling this into the AWS non-try build image today. This only a handful of instances, but hopefully we will be crossing over to AWS fully within the week. Grenade is going to handle updating the try AMI.

yasm in ec2/spot try was already at 1.2 I have bumped it to 1.3 (https://github.com/mozilla/build-cloud-tools/pull/141)

Thanks updating yasm, Rob! Resolving fixed as per comment 9.

It may have been 1.2 on some machines, but certainly not all of them as enabling features requiring yasm 1.2 cause build failures

Does that mean we can now use AVX2 on windows and others?is yasm >= 1.2 now available on some platforms? which ones?

So for Windows that works great now, and I've enabled AVX2 optimisation for the media decode. What about the other platforms? in particular mac. Linux doesn't really matter as that particular code won't be used by 97% of linux users.

mac still fail to compile: https://treeherder.mozilla.org/#/jobs?repo=try&revision=a2528dc9c2fd

Ralph - do you know enough about Mac OSX tooling to help here?

Taskcluster mac builds have 1.2, per https://treeherder.mozilla.org/#/jobs?repo=try&revision=b41cef917d63&selectedJob=15298729. Waiting for confirmation on the native mac builds from the same try run.

Native builds say yasm version... 1.1.0.2352 (v1.1.0) so the images need updating. I don't know where that lives, but will ask.

The excellent jlund points me at https://hg.mozilla.org/build/puppet/log/tip/modules/packages/manifests/yasm-dmg.sh last touched by...dustin. Can you help us out with the bump?

Sure, that's the script to build the new DMG. How can I help?

I've updated the script to build yasm 1.3.0 in bug 1238798. Can you take care of review and getting that deployed?

Jean-Yves, can we close this now?

taking this into 1240627 for mac. We still have Linux to take care off. It's currently yasm 1.1

I'm going to un-ni myself because we're sorted for Windows at least.

I'm going to close this. Linux beta builds use yasm 1.2.0.

Removing leave-open keyword from resolved bugs, per :sylvestre.