macdeployqt otool parsing broken

I built Qt from the tip of the 5.6 branch on May 5 and using macdeployqt from that build with our application is successful. However, using a build I made yesterday, May 19, from the tip of the 5.6 branch fails.

I believe the failure is caused by 75b595a6867652cc2b3ff8b2749f91236b6cb58c (QTBUG-47868, https://codereview.qt-project.org/#/c/156453/). My reasoning for this accusal is only that this change was introduced between the dates I give above and because it appears to deal with the area of macdeployqt that is failing. I haven't done any serious investigation however.

The specific failure I'm getting in macdeployqt is this:

Log: Using otool:
Log:  inspecting "Igor64.app/Contents/Libraries/libtbb.dylib"
Log: Using otool:
Log:  inspecting "/usr/lib/mac64mac64"
ERROR: "error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/otool: can't open file: /usr/lib/mac64mac64 (No such file or directory)\n"

I have attached the complete output of the command

macdeployqt Igor64.app -verbose=3

using both the "broken" version (built on May 19) and the working version (built on May 5).

Here is the otool -L output of the libtbb.dylib file that macdeployqt is failing on:

adam-lights-mac-pro ~/Documents/IgorDev/IgorGit/IgorPhoenixFolder: otool -L ../igorsrc7/IntelTBB/lib/libtbb.dylib 
../igorsrc7/IntelTBB/lib/libtbb.dylib:
	libtbb.dylib (compatibility version 0.0.0, current version 0.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.1.4)
	mac64/libcilkrts.5.dylib (compatibility version 0.0.0, current version 0.0.0)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.4.0)
	/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)

It seems that the

mac64/libcilkrts.5.dylib

path is causing problems with macdeployqt.

For what it's worth, I'm still using Xcode 6.4, which I realize is out of date and possibly no longer supported by Qt.

Also, if I use the version of macdeployqt that was created from the build I made on May 5 instead of the one from May 19 (with everything else staying the same), I am able to successfully deploy my application.

If you need more information, please let me know what I can provide.