----- Original Message -----
From: "David Oswald"
One place I read mentioned that the fix was to specify that the linker
include libstdc++. So that brings me to Inline::CPP version 0.38_003.
Here's another fail:
http://www.cpantesters.org/cpan/report/01b0da7c-76d9-11e1-b744-2613173997d5
Same failure point. All new Makefile.PL (using ExtUtils::CppGuess).
The reason I point to this report is because you'll find in all of the
0.38_003 reports diagnostic information from test 08cppguess.t that
tells us which compiler and libraries are being selected in
Makefile.PL. It can be seen that we are indeed linking with
libstdc++.
Yes, but does libstdc++ get found ? If not, EU::MM will silently remove the
link (unless a noisy build is requested - in which case you'll see a warning
that the library could not be found).
I::CPP always includes the -lstdc++ link for me on Windows/MinGW - but the
library doesn't get found. This doesn't matter (since it's apparently not
needed).
Whenever I build "noisy" I see:
Starting Build Compile Stage
Starting "perl Makefile.PL" Stage
Note (probably harmless): No library found for -lstdc++
Writing Makefile for try_pl_2608
Writing MYMETA.yml and MYMETA.json
Finished "perl Makefile.PL" Stage
But if I have a successful build without "noisy" turned on, I see nothing
that indicates that libstdc++ was not found.
(Note that if EU::MM fails to find a library, it also automatically removes
the link to that library, thereby preventing the build from failing. This is
a great convenience when you know that you have to link to either libone or
libtwo, but don't which of the 2 libs will be found on the users machine.
You just do '-lone -ltwo' and EU::MM takes care of the rest.)
Cheers,
Rob
