You can check the configuration of the currently installed system-perl with 'perl -V'. This will issue more information than you ever wanted to know about a Perl install which you could then use as a template for the new build... <br>
<br>But, off hand I'd say leave the defaults as-is unless you have something esoteric planned... in my experience the '-Dprefix=/path/to/install' is the most usefull option with Configure.<br><br>Hope that helps,<br>
m<br><br><div class="gmail_quote">On Tue, Apr 13, 2010 at 3:23 PM, Tim McDaniel <span dir="ltr"><<a href="mailto:tmcd@panix.com">tmcd@panix.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I'm running ./Configure in preparation for building perl.<br>
/etc/redhat-release is Red Hat Enterprise Linux Server release 5.3<br>
(Tikanga).<br>
<br>
I'm inclined to just accept the defaults for everything (except I did<br>
"./Configure -Dprefix=/opt/perl/perl-5.10.1" so that it has its own<br>
playpen). But I'm uncertain about threading support and multiplicity.<br>
The defaults are "n"; should I select either or both? If I want code<br>
to run under Apache, maybe using mod_perl, should the answers change?<br><font color="#888888">
<br>
-- <br>
Tim McDaniel, <a href="mailto:tmcd@panix.com" target="_blank">tmcd@panix.com</a><br>
_______________________________________________<br>
Austin mailing list<br>
<a href="mailto:Austin@pm.org" target="_blank">Austin@pm.org</a><br>
<a href="http://mail.pm.org/mailman/listinfo/austin" target="_blank">http://mail.pm.org/mailman/listinfo/austin</a><br>
</font></blockquote></div><br>