Closed wbraswell closed 5 years ago
This is a continuation of the fixes for open issue: https://github.com/ingydotnet/inline-c-pm/issues/72
Several non-GCC compilers have shown error messages which do not exactly match the GCC errors we were previously expecting: http://www.cpantesters.org/cpan/report/80aa99a2-1e12-11e9-9fb5-f9dfb1e56781 http://www.cpantesters.org/cpan/report/79f91110-1e12-11e9-9fb5-f9dfb1e56781 http://www.cpantesters.org/cpan/report/8f87b680-1e12-11e9-9fb5-f9dfb1e56781
I have simplified the expected errors to be more generic, now we are only detecting 2 strings: "error" and "COMPILERERROR".
This should work on all compilers, although if we see more failures then I can try to simplify the expected errors even more.
This is a continuation of the fixes for open issue: https://github.com/ingydotnet/inline-c-pm/issues/72
Several non-GCC compilers have shown error messages which do not exactly match the GCC errors we were previously expecting: http://www.cpantesters.org/cpan/report/80aa99a2-1e12-11e9-9fb5-f9dfb1e56781 http://www.cpantesters.org/cpan/report/79f91110-1e12-11e9-9fb5-f9dfb1e56781 http://www.cpantesters.org/cpan/report/8f87b680-1e12-11e9-9fb5-f9dfb1e56781
I have simplified the expected errors to be more generic, now we are only detecting 2 strings: "error" and "COMPILERERROR".
This should work on all compilers, although if we see more failures then I can try to simplify the expected errors even more.