Well, you could kick out all the documentation and probably most modules. The list below is probably a good starting list of modules you'll need: 

perl -Mstrict -Mwarnings -MFile::Copy -mFile::Path -e'print "$_\n" for
+ sort keys %INC'
Carp.pm
Config.pm
Exporter.pm
File/Basename.pm
File/Copy.pm
File/Path.pm
File/Spec.pm
File/Spec/Unix.pm
re.pm
strict.pm
vars.pm
warnings.pm
warnings/register.pm

[download]
Also, as far as I know the "architecture" is the architecture your perl is build for, not the arch it was build on. That probably means you can't reliably run i686 perl on i586 at all. You might want to build a 486 perl if you're concerned about portability.

"What should it profit a man, if he should win a flame war, yet lose his cool?"

In reply to Re: Minimal Perl by Joost
in thread Minimal Perl by carcassonne

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.