See #18865. Cause is an OS install is, for some reason, causing VisIt to look for its binaries in darwin-i386 instead of darwin-x86_64. I think Rosetta may be cause. Maybe we should just create a symlink in the install point as part of our package so that when user's install VisIt, it can find its binary components through either path.
Alternatively, maybe we've got to fix logic in our launcher script to correctly assess architecture for these newer macOS OSs.
cyrush
commented
1 year ago
See #18865. Cause is an OS install is, for some reason, causing VisIt to look for its binaries in
darwin-i386instead ofdarwin-x86_64. I think Rosetta may be cause. Maybe we should just create a symlink in the install point as part of our package so that when user's install VisIt, it can find its binary components through either path.Alternatively, maybe we've got to fix logic in our launcher script to correctly assess architecture for these newer macOS OSs.