Build issues for mac x86_64 and mac arm64

[markcmiller86]

Description

Resolves #

Type of change

• Bug fix~~
• New feature~~
• Documentation update~~
• Other~~

How Has This Been Tested?

Reminders:

• Please follow the style guidelines of this project.
• Please perform a self-review of your code before submitting a PR and asking others to review it.
• Please assign reviewers (see VisIt's PR procedures for more information).

Checklist:

• I have commented my code where applicable.~~
• I have updated the release notes.~~
• I have made corresponding changes to the documentation.~~
• I have added debugging support to my changes.~~
• I have added tests that prove my fix is effective or that my feature works.~~
• I have confirmed new and existing unit tests pass locally with my changes.~~
• I have added new baselines for any new tests to the repo.~~
• I have NOT made any changes to protocol or public interfaces in an RC branch.~~

[markcmiller86]

So, on x86_64, ospray is building but apparently using tbb from system install point...

#ospray: INVALID device --> Load of ospray_module_cpu failed due to: 'could not open module lib ospray_module_cpu:
dlopen(/Users/miller86/visit/visit/34rc/release/build-mb-3.4.2-darwin-22-x86_64-release/thirdparty_shared/third_party/ospray/3.0.0/darwin-x86_64/ospray/lib/libospray_module_cpu.3.0.0.dylib, 0x0005):
Library not loaded: /usr/local/opt/tbb/lib/libtbb.12.dylib

Now, I've done what I can to eliminate /usr/local/opt from my path and it is still finding useful stuff there. Presumably there is logic in ospray that goes and looks in the usual places for stuff whether you asked it to or not.

I wonder if temporarily moving /usr/local/opt out of the way when doing release builds would be a good thing to do.

[markcmiller86]

Wait a minute, I don't have a /usr/local/opt on my system