LibCxxOnOlderSystems - and more software that is pushing for gcc

[Ken Cunningham]

> 
> Why would the Fortran compiler link its build products against
> libstdc++? Are you seeing this behavior?


> Please provide evidence that these ports are actually using g++. If they
> are, then they should be fixed to not do so. If they are not and are
> only using gcc and/or gfortran, then *there is no problem*.

> 
> FWIW, I have py35-numpy+gcc6 installed, and none of its object files
> link to libstdc++, although many of them do link to MacPorts'
> libgcc_s.1.dylib.
> 
> % port -q contents py35-numpy | xargs otool -L | fgrep 'libstdc++'
> % echo $?
> 1


Lawrence, perhaps you've hit upon the final answer to this, then.

gcc6 is required for some ports, and gets pulled in -- but apparently only for it's fortran compiler (at least if what you've said about it being a macports bug to use g++ holds true).

And although the fortran compiler is written in C and C++ (according to the gcc fortran website) it does not in the end actually link it's output binaries to libstdc++ (as you've just demonstrated) so there is no worry about letting it proceed to completion on a system running Macports on 10.11, or any other version, including LibCxxOnOlderSystems.

So it's a "non problem", in the end.

Thanks, everyone. I always learn something from these brief discussions.

Ken