Re: [Users] [ET Trac] [Einstein Toolkit] #1471: Cactus should auto-detect newer versions of GCC from MacPorts
On 30 Apr 2018, at 16:30, Einstein Toolkit trac-noreply@einsteintoolkit.org wrote:
#1471: Cactus should auto-detect newer versions of GCC from MacPorts --------------------------+--------------------------------- Reporter: Ian Hinder | Owner: (none) Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus | Version: development version Resolution: | Keywords: --------------------------+---------------------------------
Comment (by Steven R. Brandt):
Ian, gcc -version showed that it was clang.
And is this the compiler that Cactus picked up?
AFAIK, if it compiles with generic.cfg, it has to use the "gcc" that's in the path.
--Steve
On 04/30/2018 03:37 PM, ian.hinder@aei.mpg.de wrote:
On 30 Apr 2018, at 16:30, Einstein Toolkit <trac-noreply@einsteintoolkit.org mailto:trac-noreply@einsteintoolkit.org> wrote:
#1471: Cactus should auto-detect newer versions of GCC from MacPorts --------------------------+--------------------------------- Reporter: Ian Hinder | Owner: (none) Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus | Version: development version Resolution: | Keywords: --------------------------+---------------------------------
Comment (by Steven R. Brandt):
Ian, gcc -version showed that it was clang.
And is this the compiler that Cactus picked up?
-- Ian Hinder http://members.aei.mpg.de/ianhin
Trac mailing list Trac@einsteintoolkit.org http://lists.einsteintoolkit.org/mailman/listinfo/trac
On 1 May 2018, at 15:47, Steven R. Brandt 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.
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
users@lists.einsteintoolkit.org
-
ian.hinder＠aei.mpg.de -
Steven R. Brandt