At 3:52 PM -0800 2/12/01, Peter Prymmer wrote:
>There are four documents since the [.porting]glossary. document also
>gives information on what various OS and C RTL variables imply (as well as
>the comments within config_h.SH).
Thanks, Peter. There's now so much documentation we need
documentation to navigate the documentation, or at least *I* do.
Then again, I can always ask you when I get stuck :-).
> we do
>not check to see if someone said:
>
> @configure "[EMAIL PROTECTED]"
Hmm. That's what I thought.
>But that is actually a build time issue - for installation you want to
>edit the values in Config.pm in you installed PERL_ROOT. Folks can still
>do that if they like. The intricacies of setting ones Config.pm properly
>is one of the big arguments in favor of building perl yourself from
>source.
Agreed. I suppose one could also edit config.h after configuring and
before building. But I'm looking for ways to productionize the
creation of pre-built kits since there seems to be some interest in
that and those with unusual hardware/software environments are not
always those well-versed in customizing a Perl configuration.
--
____________________________________________
Craig A. Berry
mailto:[EMAIL PROTECTED]
