I have no issues when using g++,
$ cpanp i Inline::CPP
Installing Inline::CPP (0.25)
Running [C:\perl\5.10.1\bin\MSWin32-x86-multi-thread\perl.exe C:\perl\
+5.10.1\bin\cpanp-run-perl *snip*\CPANPL~1\510~1.1\build\Inline-CPP-0.
+25\Makefile.PL]...
This will configure and build Inline::C++.
What default C++ compiler would you like to use? [g++]
What default libraries would you like to include? [-lstdc++]
Checking if your kit is complete...
Looks good
Writing Makefile for Inline::CPP::grammar
Writing Makefile for Inline::CPP
Running [C:\perl\dmake-4.12-20090907-SHAY\dmake\dmake.EXE test]...
C:\perl\5.10.1\bin\MSWin32-x86-multi-thread\perl.exe "-MExtUtils::Comm
+and::MM" "-e" "test_harness(0, 'blib\lib', 'blib\arch')" t/*.t
t/01basic.t ... ok
t/02prefix.t .. ok
All tests successful.
Files=2, Tests=14, 19 wallclock secs ( 0.08 usr + 0.03 sys = 0.11 CP
+U)
Result: PASS
C:\perl\5.10.1\bin\MSWin32-x86-multi-thread\perl.exe "-MExtUtils::Comm
+and::MM" "-e" "test_harness(0, '..\blib\lib', '..\blib\arch')" t/*.t
t/01nherit.t .. ok
t/02scope.t ... ok
t/03inline.t .. ok
t/04const.t ... ok
t/05virt.t .... ok
t/06deflt.t ... ok
t/07static.t .. ok
t/08anon.t .... ok
t/09purevt.t .. ok
t/10struct.t .. ok
t/11minhrt.t .. ok
t/12retlst.t .. ok
t/13vararg.t .. ok
t/14const.t ... ok
t/15stvar.t ... ok
t/16varlst.t .. ok
All tests successful.
Files=16, Tests=34, 98 wallclock secs ( 0.09 usr + 0.02 sys = 0.11 C
+PU)
Result: PASS
You could try
Bug #45168 for Inline-CPP: The Makefile.PL does not properly set the library path on a mac. A patch is attached.
Bug #42552 for Inline-CPP: All tests fail on recent debian/g++ versions. "iostream.h" not found problem.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|