Changes between Initial Version and Version 1 of Ticket #54766, comment 19


Ignore:
Timestamp:
Sep 7, 2017, 9:28:46 AM (7 years ago)
Author:
RJVB (René Bertin)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #54766, comment 19

    initial v1  
    44> 1. If GCC is **not** installed, does {{{-stdlib=macports-libstdc++}}} cause a compile-time error or silently do the wrong thing?
    55
    6 As far as I can tell your patch uses a hardcoded full path to the MacPorts libstdc++ . That should fail if the library isn't there.
     6As far as I can tell your patch uses a hardcoded full path to the MacPorts libstdc++ . That should fail if the library isn't there. Should be quick and easy to test (just move the MacPorts libstdc++.6.dylib file aside or deactivate port:libgcc).
    77
    88> 1. To avoid multiple recompilations of clang, can {{{-stdlib=macports-libstdc++}}} now use gcc7 header files?
    … …  
    1010It looks like gcc7 was finally bumped to the current 7.2 release which means that libgcc is now also at 7.2.0 . I think that means you *have* to use those.
    1111
    12 Let me reiterate my suggestion to move the libstdc++ headerfiles into libgcc - what do you think Jeremy?
     12Let me reiterate my suggestion to move the libstdc++ headerfiles into libgcc - what do you think Jeremy? At the very least port:libgcc could install a symlink to where the headerfiles ought to be installed
    1313
    1414That's a separate ticket of course and shouldn't require clang rebuilds. I can try to look into that as part of my tinkering with the gcc7 port.