<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jan 31, 2020, at 9:50 AM, gregor herrmann <<a href="mailto:gregoa@debian.org" class="">gregoa@debian.org</a>> wrote:</div><div class=""><div class=""><br class="">In my understanding, ExtUtils::HasCompiler is there for situations<br class="">where the presence of a compiler is not guaranteed.<br class=""></div></div></blockquote><div><br class=""></div><div>Right. If I don't do this then I get all sorts of testing failure reports about systems which don't have a compiler.</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">In Debian, we know that we have a compiler when building packages, so<br class="">the check doesn't bring any advantage, and unless I'm missing<br class="">something we could just patch it out.<br class=""><br class=""></div></div></blockquote></div><br class=""><div class="">Given your expertise and control over the build environment, I think its perfectly reasonable for you to disable the compiler check and let it move on. </div><div class=""><br class=""></div><div class="">I don't think it makes sense for me to add an exception to Makefile.PL but if you have any ideas, patches are welcome. <a href="https://github.com/toddr/YAML-Syck" class="">https://github.com/toddr/YAML-Syck</a>. </div><div class=""><br class=""></div><div class="">Possibly we could enhance ExtUtils::HasCompiler to look for a environment variable that indicates that it is in a build system and coerces it to pass without a check. I'm speaking with the author about this now.</div><div class=""><br class=""></div><div class="">Todd</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>