ffmpeg: builds succeeding for MacOS 10.6, but buildbots not deploying public binaries

[mascguy (Christopher Nielsen)]

When updating ports on my MacOS 10.6 VM, ffmpeg curiously built from source.

Checking the port status page, all builds - including 10.6, both 64-bit and 32-bit - are succeeding:

​https://ports.macports.org/port/ffmpeg/builds

And looking at the last 10.6_64 build, nothing appears to be amiss. Well, apart from the fact that it's unclear whether the binary is being properly copied:

​https://build.macports.org/builders/ports-10.6_x86_64-builder/builds/53614/steps/deploy-archives/logs/stdio

Of note, there don't appear to be any Darwin 10 binaries for this port, 64-bit or 32-bit:

​https://packages.macports.org/ffmpeg

Is this known/expected...?

[mascguy (Christopher Nielsen)]

There's one possibility I didn't consider: If the dependencies are different from 10.6 vs. later MacOS releases - and the license for one of the dependencies precludes publishing binaries - that could explain it.

But want to confirm that there isn't some other type of issue...

[mascguy (Christopher Nielsen)]

In terms of additional dependencies, there are two:

• legacy-support (used for MacOS 10.6-10.12)
• libcxx (only used for MacOS 10.6)

[jmroot (Joshua Root)]

​https://build.macports.org/builders/ports-10.6_x86_64-builder/builds/53614/steps/gather-archives/logs/stdio

Probably via the clang-9.0 dependency.

[mascguy (Christopher Nielsen)]

I'm seeing the following:

"ffmpeg" is not distributable because its license "gpl" conflicts with license "OpenSSL" of dependency "openssl"

Clang 9 is being used to compile ffmpeg for other MacOS releases though.

I'm curious why the openssl dependency is an issue for MacOS 10.6 builds, but not later releases...?

[mascguy (Christopher Nielsen)]

I found the following ticket, related to MacPorts-provided compilers and the openssl license. But it was fixed 19 months ago:

issue:57460 - Use of MacPorts clang compilers causes GPL ports to become nondistributable because of openssl

Josh, it looks like python-27 is a library dependency for clang-9.0, but only on MacOS 10.6. And that's another port that depends on openssl.

Could that be the cause...?

[mascguy (Christopher Nielsen)]

Jeremy/Ken,

I'm trying to track down the cause of this ticket. And I noticed that clang-9.0 has a lib dependency on python-27, for MacOS 10.6 and earlier.

Does Clang 9 actually require Python 2.7 at runtime? Or is Python only used for the build?

[kencu (Ken)]

I can look. It's a build dep, for sure, to process the python stuff in the llvm tree.

dunno why it's a lib dep just at the moment.

[ryandesign (Ryan Carsten Schmidt)]

Replying to mascguy:

I'm trying to track down the cause of this ticket.

We would get more detailed information if we finished and merged ​https://github.com/macports/macports-infrastructure/pull/14

[mascguy (Christopher Nielsen)]

Replying to ryandesign:

We would get more detailed information if we finished and merged ​https://github.com/macports/macports-infrastructure/pull/14

I've reached out to the author to see if he's willing to complete that, or have someone else finish it.

Ditto for his related PR:

​https://github.com/macports/macports-base/pull/211

[kencu (Ken)]

it doesn't seem to me that everything built with clang-9.0 on 10.6.8 (which is pretty much everything) has been non-distributable.

why would it be thought that is the case with ffmpeg exactly?

[mascguy (Christopher Nielsen)]

Replying to kencu:

it doesn't seem to me that everything built with clang-9.0 on 10.6.8 (which is pretty much everything) has been non-distributable.

why would it be thought that is the case with ffmpeg exactly?

That's what we're trying to figure out. Thoughts/ideas?

[kencu (Ken)]

whatever it is has nothing to do with clang-9.0?

[mascguy (Christopher Nielsen)]

Well, my only theory was that perhaps the python27 lib dependency for clang-9.0 - which is only for MacOS 10.6 and earlier - might be coming into play.

[mascguy (Christopher Nielsen)]

Even if Python isn't the issue, it would be great to update the various LLVM-related ports to declare Python as a build dependency, rather than lib.

[kencu (Ken)]

That's what I meant -- if it was clang-9.0, nothing would be distributable. But almost everything else is, ergo ... not clang-9.0 (presumably, IMHO, YMMV, etc).

python27 is actually a lib dep for clang-9.0 for 10.6.8 -- in various manifestations that (up to now) have not been worth working around.

[mascguy (Christopher Nielsen)]

Relative to resolving the ffmpeg binary publish issue, we could potentially add license_noconflict openssl. But I'm reluctant to go that route, until we understand what downstream dependency is the culprit.

[mascguy (Christopher Nielsen)]

Duplicate of issue:54633