My belief is that it's all been fixed--apart from whatever goes wrong with Memory Test. If you could test that this is so on ports, that would be great.
--Steve
On 05/01/2018 12:07 PM, ian.hinder@aei.mpg.de wrote:
On 1 May 2018, at 15:47, Steven R. Brandt <sbrandt@cct.lsu.edu mailto:sbrandt@cct.lsu.edu> wrote:
AFAIK, if it compiles with generic.cfg, it has to use the "gcc" that's in the path.
And when homebrew has its own version of gcc, does it put it on the path under the name "gcc"? What does "which gcc" give you?
If it is indeed compiling OK with Clang, it's interesting, because when I tried to compile just Cactus, not even the whole ET, using Clang on a Mac, I ran into several incompatibilities. This was a couple of years ago now, and maybe they have all been fixed.
-- Ian Hinder http://members.aei.mpg.de/ianhin