2 ms·
This binary is so universal that `file` utility gets confused about it. $ file /Volumes/TinyClock/TinyClock.app/Contents/MacOS/TinyClock /Volumes/Tiny
by grishka 4y ago
This binary is so universal that `file` utility gets confused about it.
$ file /Volumes/TinyClock/TinyClock.app/Contents/MacOS/TinyClock
/Volumes/TinyClock/TinyClock.app/Contents/MacOS/TinyClock: Mach-O universal binary with 3 architectures: [i386:Mach-O executable i386
- Mach-O executable i386] [ppc:Mach-O executable ppc
- Mach-O executable ppc] [arm64:Mach-O 64-bit executable arm64Mach-O 64-bit executable arm64]
/Volumes/TinyClock/TinyClock.app/Contents/MacOS/TinyClock (for architecture i386): Mach-O executable i386
/Volumes/TinyClock/TinyClock.app/Contents/MacOS/TinyClock (for architecture ppc): Mach-O executable ppc
/Volumes/TinyClock/TinyClock.app/Contents/MacOS/TinyClock (for architecture arm64): Mach-O 64-bit executable arm64
- JonathonW 4y agoIt's not confused; as noted in Known Bugs: > Unlike done in previous project, netop Tiger SDKs (used to build several intermediate binaries) don’t contain 64-bit AppKit versions, and thus ppc64 and x86_64 binaries are excluded from the binary release. The binary release is only three-architecture; it does not run on current Intel MacOS since it's missing an x86_64 segment. (You get a "this app needs to be updated" dialog if you try.)