At 10:05 PM -0400 4/9/02, Michael G Schwern wrote: >My Config.pm built on OpenVMS is missing... > > installprefix > installprefixexp > installsitebin > prefixexp > siteprefix > siteprefixexp > vendorarch > vendorbin > vendorbinexp > vendorlib > vendorprefix > vendorprefixexp
Not strictly true. In bleadperl we have these: d_vendorarch='undef' d_vendorlib='undef' prefixexp='perl_root:' vendorarchexp='' vendorlib_stem='' vendorlibexp='' It looks like you've been provided with ways to check whether it's kosher to use vendorarch and vendorlib. >The vendor stuff isn't so important, but siteprefix, installprefix and >installsitebin are. Hmm. I can't see right off why they are important since after reading their descriptions I have no idea what they are for. I guess it wouldn't hurt to make installprefix the same as prefix, which is just C<perl_root>. The other two seem to have something to do with "add-on" pieces of some kind, though it is not clear from the documentation whether an add-on is a Perl extension, an external library used to build a Perl extension, or some external executable program used in conjunction with Perl or an extension. In the latter two cases, I can't see how I could (or would want to) specify their locations at configuration time. In the case of Perl extensions, there are lots of other config variables that already say where things should go (if there weren't, we couldn't have been installing extensions successfully for lo these many years). So, I'll be happy to doctor up configure.com when I know what should go there, but I'm not confident about guessing what that should be. -- ____________________________________________ Craig A. Berry mailto:[EMAIL PROTECTED] "Literary critics usually know what they're talking about. Even if they're wrong." -- Perl creator Larry Wall
