libvpx on 10.5 and earlier

Ryan Schmidt ryandesign at macports.org
Wed Dec 13 16:27:04 UTC 2017


On Dec 13, 2017, at 01:10, Riccardo Mottola wrote:

> On 2017-12-11 22:15:23 +0100 Ryan Schmidt wrote:
> 
>> According to
>> https://github.com/macports/macports-ports/commit/5c48aa5a22139aedc616ff5ee173f9ca021580e0
>> support for Mac OS X 10.5 and earlier was removed in libvpx 1.5.0, so you would need to build an earlier version than that.
>> https://trac.macports.org/wiki/howto/InstallingOlderPort
> 
> 
> I can attempt that, however, also to debug the integrated libvpx of TTF/Firefox, I downloaded 1.5 and also latest 1.6.1
> 
> I am able to build "off tree" by using the macports clang compiler latest libvpx 1.6.1
> 
> CC=clang-mp-3.4 CXX=clang++-mp-3.4 ./configure
> 
> Builds happily. I tired the testsuite which did take hefty 7h 30' to run and downloaded several gigabytes
> 
> 
> [==========] 501 tests from 60 test cases ran. (26941271 ms total)
> [  PASSED  ] 495 tests.
> [  FAILED  ] 6 tests, listed below:
> [  FAILED  ] VP8MultiThreaded/TestVectorTest.MD5Match/111, where GetParam() = (0x3ab4dc, (0, 2, 0x35a479 pointing to "vp80-04-partitions-1405.ivf"))
> [  FAILED  ] VP8MultiThreaded/TestVectorTest.MD5Match/161, where GetParam() = (0x3ab4dc, (0, 3, 0x35a313 pointing to "vp80-03-segmentation-1414.ivf"))
> [  FAILED  ] VP8MultiThreaded/TestVectorTest.MD5Match/201, where GetParam() = (0x3ab4dc, (0, 4, 0x35a0bf pointing to "vp80-00-comprehensive-016.ivf"))
> [  FAILED  ] VP8MultiThreaded/TestVectorTest.MD5Match/221, where GetParam() = (0x3ab4dc, (0, 4, 0x35a2d7 pointing to "vp80-03-segmentation-1410.ivf"))
> [  FAILED  ] VP8MultiThreaded/TestVectorTest.MD5Match/281, where GetParam() = (0x3ab4dc, (0, 5, 0x35a29b pointing to "vp80-03-segmentation-1408.ivf"))
> [  FAILED  ] VP8MultiThreaded/TestVectorTest.MD5Match/421, where GetParam() = (0x3ab4dc, (0, 7, 0x35a479 pointing to "vp80-04-partitions-1405.ivf"))
> 
> 
> Maybe this is acceptable? I don't know how it fares on 10.6 and up, this is a 32bit build.
> What compiler is the port using? Maybe PPC would fail, but intel builds.

To determine what compiler a port is using, examine the debug output (sudo port -d install whatever) or the main.log file $(port logfile whatever)


> I also tried compiling even 1.5 with gcc 4.8 and gcc 6, but it fails the same way the integrated libvpx of TTF fail.
> I looked int othe code and it fails with assembler issues, the original coder noted that it is for gcc 4.7 and clang 3.4 up, so it should work!
> Apparenltly the issue is that our MP cc uses an "old" linker that doesn't support those instrucions, there are several posts around. Are we?

If you want the new linker, install the ld64 port.




More information about the macports-users mailing list