Opened 4 years ago
Closed 3 years ago
#62851 closed defect (duplicate)
ffmpeg: builds succeeding for MacOS 10.6, but buildbots not deploying public binaries
Reported by: | mascguy (Christopher Nielsen) | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | buildbot/mpbb | Version: | |
Keywords: | Cc: | jeremyhu (Jeremy Huddleston Sequoia) | |
Port: | ffmpeg |
Description
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:
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...?
Change History (19)
comment:1 Changed 4 years ago by mascguy (Christopher Nielsen)
comment:2 Changed 4 years ago by 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)
comment:4 Changed 4 years ago by 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...?
comment:5 Changed 4 years ago by 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...?
comment:6 Changed 4 years ago by mascguy (Christopher Nielsen)
Cc: | kencu added |
---|
comment:7 follow-up: 9 Changed 4 years ago by 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?
comment:8 Changed 4 years ago by 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.
comment:9 follow-up: 10 Changed 4 years ago by 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
comment:10 Changed 3 years ago by 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:
comment:11 follow-up: 12 Changed 3 years ago by 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?
comment:12 Changed 3 years ago by 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?
comment:14 Changed 3 years ago by 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.
comment:15 Changed 3 years ago by 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.
comment:16 Changed 3 years ago by 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.
comment:17 Changed 3 years ago by 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.
comment:18 Changed 3 years ago by kencu (Ken)
Cc: | kencu removed |
---|
comment:19 Changed 3 years ago by mascguy (Christopher Nielsen)
Resolution: | → duplicate |
---|---|
Status: | assigned → closed |
Duplicate of issue:54633
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...