I didn’t see this thread back when it was current, but for future reference, when someone has a problem like this, put env as the first command in your build script. That’s the only way to know for 100% certain what your PATH etc values actually are. (Many times these kinds of problems are caused by some build server running your script in an environment that is not set up the way you expect it–not running the profile or rc files you think it is, or forking a process with environment variables cleared.)

Would you be willing to do a screen share later today? I’m in US/Eastern time zone. I could do it at 9:30 PM… Maybe some brainstorming would help

No problem, tomorrow during the day would work - please ping me here on forum, I’ll get notified.