On Jan 1, 2021, at 11:38, Ken Cunningham wrote:
>> A similar problem is when build systems save the compiler that was used into
>> files that get installed and then try to use that compiler later to build
>> other modules; perl does this. And this causes problems like
>> https://trac.macports.org/ticket/59786. The solution is the same: replace
>> the specific compiler path in the installed files (e.g.
>> /opt/local/bin/clang-mp-3.4) with the generic compiler (/usr/bin/cc) that
>> exists on all systems.
>
>
> I don’t imagine you really mean we should change the baked in compiler for
> for perl, python, ruby, and the like to /usr/bin/cc.
>
> On some system versions, /usr/bin/clang perhaps?
I did mean /usr/bin/cc, as Josh said in
https://trac.macports.org/ticket/59786#comment:5. Why not?
If the user doesn't tell perl what compiler to use, then it should use a
compiler that exists. /usr/bin/cc always exists.
