Well observed.
$ cat 832794.c
#include <iostream.h>
$ g++ -c 832794.c
In file included from /usr/include/c++/4.2/backward/iostream.h:31,
from 832794.c:1:
/usr/include/c++/4.2/backward/backward_warning.h:32:2: warning: #warni
+ng This file includes at least one deprecated or antiquated header. P
+lease consider using one of the 32 headers found in section 17.4.1.2
+of the C++ standard. Examples include substituting the <X> header for
+ the <X.h> header for C++ includes, or <iostream> instead of the depr
+ecated header <iostream.h>. To disable this warning use -Wno-deprecat
+ed.
$ gcc -c 832794.c
832794.c:1:22: error: iostream.h: No such file or directory
...which is exactly the first error the OP is getting:
_01basic_t_5cd2.xs:2:22: iostream.h: No such file or directory
(Just to be clear: the primary issue here is not the deprecation warning, but the fact that the path were iostream.h resides isn't being searched when gcc is used. The warning is just an indication that Inline::CPP is rather old/unmaintained.)
-
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.
|
