Yep, FindBin doesn't seem to be the problem. Don't know what to say there. You can still use IMCC though.

Neither the assembler nor IMCC have anything to do with the parrot interpretter (which is actually a virtual machine). However, both the assembler and IMCC have the ability to assemble parrot assembly into parrot bytecode. Traditionally, this has been the job of the assembler, but IMCC, the optimizer, has gotten advanced enough so that it can also assemble, and is actually better at it. Give it a try! It shouldn't break like the assembler did; it is written in pure C.

In reply to Re: Re: Re: Problems compiling Parrot by jryan
in thread Problems compiling Parrot by jens

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.