Actually, and I missed this in my first reply, the ld2 line does seem to be linking the library correctly (or at least without errors): 
LD_RUN_PATH="" ld2  -s -L/usr/local/lib _04perlapi_t_3c76.o  -o blib/a
+rch/auto/_04perlapi_t_3c76/_04perlapi_t_3c76.dll /usr/lib/perl5/5.8.0
+/cygwin-multi-64int/CORE/libperl.dll.a

[download]
It does -o blib/arch/auto/_O4perlapi_t_3c76/_04perlapi_t_3c76.dll. This creates the dll in that directory (-o specifies the output file of the linking operation). So the problem occurs somewhere between this line (inclusive) and the chmod line further downstream. What's in blib/arch/auto/_04perlapi_t_c76 after you did the above steps?

CU
Robartes-

In reply to Re^3: Problem with compiling Inline::C on cygwin by robartes
in thread Problem with compiling Inline::C on cygwin by zby

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.