Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

"Now comes a very long list of questions, which must be answered somehow. In most cases, just hitting return (accepting the default) works."

Given the above statement and the discussion in the CB and via /msg today on the subject of Configure, it may be a good idea (though some may consider it stating the obvious) to suggest that people building perl in from source read and understand the README file, the INSTALL file and any platform specific readme file as a minimal primer to familiarise themselves with the configuration/installation process and associated terminology.

In the grand scheme of things, we're not talking about reading an excessive amount of documentation here. It's also good practice for new users to familiarise themselves with perls style of documentation.

The README file shows an example installation, explaining calling Configure with the -des flag to accept the default values, along with an an installation prefix:



If you're using a relatively modern operating system and want to install this version of Perl locally, run the following commands:

./Configure -des -Dprefix=$HOME/localperl make test make install

The INSTALL file elaborates on this in the Run Configure section, explains how to pass exactly the configuration parameters you want, while accepting the defaults for other things and how to accept defaults after any point of an interactive configure run. That said, you may not know you're happy to skip any of these options, until you've been through the process at least once ;)


In reply to Re: Building a Development Environment on Ubuntu by marto
in thread Building a Development Environment on Ubuntu by Xiong

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others examining the Monastery: (6)
    As of 2018-01-17 02:09 GMT
    Find Nodes?
      Voting Booth?
      How did you see in the new year?

      Results (194 votes). Check out past polls.