<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 20, 2018, at 1009 , Rainer Müller <<a href="mailto:raimue@macports.org" class="">raimue@macports.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On 2018-06-20 03:19, Lee Bast wrote:<br class=""><blockquote type="cite" class=""><span class="Apple-tab-span" style="white-space:pre"> </span>Just wanted to give a small follow up: in the end I think the mpv port is just entirely broken for me. I kept trying things until I ended up doing a total fresh install again following updating to Xcode 9.4. Starting entirely from scratch and just doing a plain "port install mpv" with no variants or anything else installed first I still get the exact same error where configure fails on<br class=""><br class=""><blockquote type="cite" class="">:info:configure Checking for Lua : no ('lua-5.2 >= 5.2.0' not found) <br class=""></blockquote></blockquote><br class="">Just checking, is the lua52 port installed and active?<br class=""></div></div></blockquote><div><span class="Apple-tab-span" style="white-space:pre"> </span>No, I did a total clean install blowing away everything (following <a href="https://guide.macports.org/#installing.macports.uninstalling" class="">https://guide.macports.org/#installing.macports.uninstalling</a>) then tried 'port install mpv' as the very first port following self-update. lua52 is a dependency of mpv, so like any other port it's installed first along with all other not present dependencies before it finally gets to mpv right? In my first encounter (back on June 7th) of the problem if I manually installed lua then that check would pass, except that then it would immediately fail on the next dependency, and so on. I can't think of any other port where there is a need to manually install every single dependency unless the user wants a custom variant or to try to force the use of something non-default (like libressl vs openssl). I don't think lua specifically is the issue here, rather it's something in how the port is handling dependency installation, or some other interaction.</div><div><br class=""></div><blockquote type="cite" class=""><div class=""><div class="">The problem can probably only be debugged further by looking into<br class="">config.log, which contains the details how and where mpv expected to<br class="">find Lua. Use this command to find this file after the failed build attempt:<br class=""><br class="">$ find $(port work mpv) -name config.log<br class=""></div></div></blockquote><div><span class="Apple-tab-span" style="white-space:pre"> </span>Here you go:</div><div></div></div></body></html>