Open hakonhagland opened 2 years ago
Basically the linker is worried about the object files (in the libpython static library) using features that the linker doesn't support; even though it probably isn't. Typical Apple being difficult.
Is this something that should be changed in ExtUtils::MakeMaker or in the Makefile.PL of Inline::Python ?
The value comes from perl's configuration, MakeMaker is entirely right to use that. If something needs to be changed it's there, though I'm not sure if it should.
I am trying to build
Inline::Python
on macOS 12.0.1. I installed perl 5.34.0 with perlbrew before I upgraded my mac from 11.4 to 12.0, this can be seen by runningwhere
-mmacosx-version-min=11.4
indicates that perl was built on macOS 11.4. I tried to figure out the meaning of this compiler flag but I could find no clear explanations on google. As I understand, it will trigger compiler warnings fromclang
if I am trying to link with a library that is built after macOS 11.4. But then again, why is the flag then not called-mmacosx-version-max
? I am confused.Anyway, after upgrading my mac to 12.0, I installed a new python library with
pyenv
, and if I now try to buildInline::Python
I get the following warnings fromclang
when runningmake
:What is the best approach to avoid this warning ? (The warning disappears if I remove
-mmacosx-version-min=11.4
from the abovecc
command line, or if I change the flag to-mmacosx-version-min=12.0
.) Is this something that should be changed inExtUtils::MakeMaker
or in theMakefile.PL
ofInline::Python
?