SimFactory should choose an appropriate cfg on a Mac.

Create issue
Issue #2126 closed
Steven R. Brandt created an issue

generic.cfg does not work on a mac because gcc doesn't exist (one needs to use gcc-7 instead, for example). Simfactory should detect and use the correct cfg file from the set generic.cfg, osx-homebrew.cfg, and osx-macports.cfg.

Keyword:

Comments (8)

  1. Roland Haas
    • changed status to open
    • removed comment

    Please see comments inline in pull request. Cannot be applied as is, and should provide some more robust error checking as well as a statement that this was actually tested by someone (since as far as I know you do not use / or had access to) a mac in the past.

  2. Steven R. Brandt reporter
    • removed comment

    Roland and I are at an impasse discussing this ticket on the pull request. Other opinions would be welcome.

  3. Steven R. Brandt reporter
    • removed comment

    I just did an experiment. I compiled on a Mac with homebrew using generic.cfg. The obvious problem with doing things this way is that "gcc" is really clang.

    However, despite Mac lying about the compiler, Cactus compiled and the test suite ran (except for Memspeed). Given this, I think we can modify the tutorial to remove the Mac-specific instructions and close this ticket.

    Ian, could you test to see if this works on a mac ports install also?

  4. Roland Haas
    • removed comment

    Looks mostly good. I have added couple of comments to the pull request.

    Cannot be pushed to master as is since it contains leftover print statements from debugging it seems. There are some minor things that should be fixed as well and one has to consider what happens on eg debian (and likely Ubuntu) systems where there is a gcc and a gcc-N but gcc is the real thing this time (and points to one of the gcc-N based on either user choice or on the distro settings and gcc is the one that is compatible with most packages provided by the distro while gcc-N may not be).

  5. Log in to comment