Yes, the line num changedThen I can't envisage the situation that leaves "write" defined to ""PerlLIO_write" - but apparently that's what's happening.
It's probably not the best way, but I'd be fiddling about with some Inline::C scripts to check on some things.
Based on the information at hand, I would think that the following Inline::C script (untested) should produce the error:
use Inline C => Config =>
BUILD_NOISY =>1,
INC => '-ID:/mydoc/projects/GenoEye-0.4.5-Source/src';
use Inline C => <<'EOC';
/*
#undef write
*/
#include <genoeye/Common.h>
EOC
and that the error should disappear once the #undef is commented in. (Though your experience suggests that that the inclusion of
#undef write into the code will make no difference.)
Cheers,
Rob
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.