Update: This is perhaps a long winded approach, but I think it helps to understand the process in full.
Download the module, extract the archive, then:
wget https://rt.cpan.org/Ticket/Attachment/1576496/841876/0001-Fix-a-p
+ad-problem-with-Perl-5.21.4-on-threaded-build.patch
marto@shemp ~/Devel-CallParser-0.002 $ patch -p1 < 0001-Fix-a-pad-prob
+lem-with-Perl-5.21.4-on-threaded-build.patch
patching file lib/Devel/CallParser.xs
patching file t/pad2.t
Notice that the patch has created the new file you're looking for (you can see everything the patch does by reading it and following the logic). Then:
marto@shemp ~/Devel-CallParser-0.002 $ cpanm .
--> Working on .
Configuring Devel-CallParser-0.002 ... OK
Building and testing Devel-CallParser-0.002 ... OK
Successfully installed Devel-CallParser-0.002
1 distribution installed
-
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.
|