Izaak "Zaak" Beekman

@nchaimov Is the solution here to always require GNU compilers on apple? We could make sure that brewed or macports installed compilers are always utilized and never clang. Are there...

Sure, but what about with tau_exec -ebs and friends? It would simplify logic to just forbid clang on Apple. Obviously, with PDT we can never use it, but I'm just...

Right. So we just need logic to ensure that when PDT is used on Apple, all tooling is built with GCC. Hopefully a compat stanza can be crafted to achieve...

Once taucmdr has support I can try running through the paces with GCC 7.2 from Homebrew (and MPICH 3.2 or OpenMPI 3.0.0)

Some notes: - It looks like both `trace2profile` and `tau_trace2json` fail due to missing `libTAU_traceinput-da6d9824` with a minimal TAU on macOS. [min-install-debug_log.txt](https://github.com/ParaToolsInc/taucmdr/files/2512407/min-install-debug_log.txt) - A full install, seems to indicate PDT...

Is PDT supposed to be supported on macOS? AFAIK, even apple's "gcc" is actually clang. GCC 8.2 is installed via homebrew on my system, and that's what PDT is picking...

Should we do some introspection and attempt to set the HOST compilers to GNU if they're found? The tricky thing is that they're probably installed with suffixes as the major...

@jlinford any ideas how to reproduce, or do you think this is fixed/invalid?

Supporting ARM64 on macOS should be feasible from the Python/TAU Commander perspective, but I'm not sure how close or how far TAU itself is from this. Either way, an appropriate...

great, then I'll think about what it would take to support it in TAU Commander & Commander Conda and if it's not a huge task try to make it happen...