Re: Perl sources and crypt()

no, you're all missing the point =P

bash$ pwd
/usr/local/nrg/src/perl-5.8.0
bash$ fgrep des_fcrypt README.*
README.win32:If you have either the source or a library that contains 
+des_fcrypt(),
README.win32:enable the appropriate option in the makefile.  des_fcryp
+t() is not
README.win32:name of the file that implements des_fcrypt().  Alternati
+vely, if
README.win32:you have built a library that contains des_fcrypt(), you 
+can set
README.win32:implementations of des_fcrypt().  Older versions have a s
+ingle,
README.win32:in des_fcrypt.patch.
README.win32:Perl will also build without des_fcrypt(), but the crypt(
+) builtin will
bash$
[download]

it's a win32ism which is why most of us who have built Perl a gazillion times have never seen it =P it's so standard on unix that it's always there. that's about all i can say.

Comment on Re: Perl sources and crypt() Download Code

Replies are listed 'Best First'.
Re: Perl sources and crypt() by Abigail-II (Bishop) on Feb 21, 2003 at 15:10 UTC
But the OP was claiming everyone who build Perl runs in into this problem. I think that the vast majority of the people who build their own perls do this on Unix, Windows users lacking a C compiler delivered with their OS rather download a binary. Had the OP not assumed there's nothing but crippled Mickeysoft OSses, people building a gazillion perls wouldn't have reacted. Abigail	[reply]