Closed kentfredric closed 2 years ago
/me blames @mohawk2
These failures started occurring in 0.15, 0.14 is the newest version tests pass for me on.
We're seeing the same issues in the conda build of this package. It would be great if the compiler name were made configurable. Xref: https://github.com/bioconda/bioconda-recipes/pull/33670
@dpryan79 What kind of configuration had you in mind? It feels to me like an environment variable would work but doesn't seem like a general solution.
@mohawk2 An environment variable (ideally $CC) would certainly work for me. In general, anything that needs a C compiler should be looking for that (or $CXX for C++ compilers).
Since this is expressly for a C++ compiler, $CXX
then?
Yes! Mea culpa on the mention of $CC :)
Ha ha, Ok! I think it would be prudent to also allow CXXFLAGS and CXXLDFLAGS to override the other two.
Released as 0.24.
FTR this new feature might have a regression, see https://github.com/tsee/extutils-cppguess/issues/26
I have a setup wherein, there is no
g++
anywhere in $PATH, nor any of the things this module looks for.Perl itself has all relevant CC and stuff passed to it during its configure/compile, but of course, perl itself doesn't have any CXX stuff in %Config.
Under this configuration, nothing I seem to be able to do fixes the problem, explicitly setting CXX in ENV doesn't help at all, and the number of places in the code that hardcode the CXX to be "g++" is ridiculous.
^ everything here is full of wrong.
( I'm explicitly setting CXX to x86_64-pc-linux-gnu-g++ in ENV, which should be enough, but it clearly is not )