twogee

The headers are in `/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Perl/5.18/darwin-thread-multi-2level/CORE/` on Mojave but that is not where Perl expects them to be.

I see no need to have an extra Perl distribution, so unless 5.20+ is necessary for other reasons, I'd like to have this Mojave oddity addressed upstream in ExtUtils::MakeMaker.

I believe that Command Line Tools put them under `/Library`. The problem is though that Perl has many other modules apart from `ExtUtils::MakeMaker` that may need to take into account...

Thanks for the tip, I prefer ``` cd /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library mv Perl Perl.off ln -s /Library/Perl # (works as well) open /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg rm Perl mv Perl.off Perl ```

For a general solution, all alternative modules for installing things must be considered, like Module::Build, ExtUtils::HasCompiler, Alien::Build. (I see ExtUtils::CBuilder has been patched.) And all "smart" modules that include their...

The second command starts an installer for headers only rather than the whole CLT. I was thinking about a symlink to /System/Library/Perl where the header files magically end up anyway,...

Perl is pretty rigid (or minimalistic 😄) with respect to placement of headers. See my comment in October regarding an extra distribution of Perl.

This is a workaround, the real fix must be done in DynaLoader.

@aanno could you please rebase and push the branch in order to close the PR?

This fixes https://issues.apache.org/jira/browse/IVY-922