@maxpietsch: OK, I’m stumped - all compiler invocations are essentially the same at this point, yet your tap version works, the standalone version doesn’t… I don’t know what the difference is, presumably running within the homebrew environment is different? I also note that the
configure script is running slightly differently - did you add the
-v option yourself, or are the versions being compiled somehow different?
One of the first things to show up differently is the explicitly
sw_vers -productVersion check in the run that errors out. Looking at the code, this seems to relate to whether the
MACOSX_DEPLOYMENT_TARGET environment variable is set (along with the related
QMAKE_MACOSX_DEPLOYMENT_TARGET). Can you try setting these explicitly in your manual run? Maybe this means our script should also set these variables explicitly right after those tests…?
Otherwise, the only things I can think of that might conceivably make a difference is indeed the
PATH. What is your
PATH when you invoke
./configure manually? I can see from your tap config that under homebrew, it’s running with:
PATH = r'/usr/local/opt/python/libexec/bin:/usr/local/opt/python/bin:/usr/local/Homebrew/Library/Homebrew/shims/super:/usr/local/opt/pkg-config/bin:/usr/local/opt/qt/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/opt/qt5/bin'
How does your default
PATH compare with that…?
I also note the temporary files are named differently for some odd reason… I have no idea why that would be the case, maybe homebrew also sets this up differently…?
In any case, I think this is probably getting a little bit too technical for the forum - let’s move the discussion over to GitHub and stop clogging up people’s inboxes…