<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; " class=""><blockquote type="cite" class="">[same as above...]<br class=""></blockquote><blockquote type="cite" class="">CMake Error at /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_multimedia_avidemux/avidemux/work/avidemux_2.7.6/cmake/admFFmpegBuild_helpers.cmake:283 (MESSAGE):<br class=""></blockquote><blockquote type="cite" class="">configure output is </opt/local/bin/clang-mp-9.0 is unable to create an<br class=""></blockquote><blockquote type="cite" class="">executable file.<br class=""></blockquote><br class="">avidemux builds it's own copy of ffmpeg, and doesn't use our MacPorts tweaks to do so.<br class=""><br class="">This particular error is caused by it forcing the use of fsanitize on darwin builds.<br class=""><br class="">On older systems, the santizers don't build, the santizer library is not found, and the fsantize option dies a horrible death.<br class=""><br class="">Patching that out was easy.<br class=""><br class="">But then there were other errors building the bundled ffmpeg that came after.<br class=""><br class="">So I personally just pegged avidemux at the last version for now <<a href="https://github.com/kencu/SnowLeopardPorts/commit/99bc24c06e2299ba86d6845853eb6a93b8ac0f43" class="">https://github.com/kencu/SnowLeopardPorts/commit/99bc24c06e2299ba86d6845853eb6a93b8ac0f43</a>> and will circle back to that later.<br class=""><br class="">In the long run, if avidemux used MacPorts' ffmpeg instead of the bundled ffmpeg, life will be much, much, much easier for us.<br class=""><br class="">Best,<br class=""><br class="">Ken</div></body></html>