this morning I couldn't get 2.0 to compile without the below changes. I guess the patch will need some #ifdefs to work with 5.9 vs 5.8 before we integrate it.

I guess I'm really behind the times, but what's the deal with perl-current? the Changes files still lists patch 18374 as the latest, but clearly there are changes going on. are people using the pre5.8.1 release instead of 5.9 these days?

--Geoff


Index: src/modules/perl/mod_perl.c =================================================================== RCS file: /home/cvspublic/modperl-2.0/src/modules/perl/mod_perl.c,v retrieving revision 1.162 diff -u -r1.162 mod_perl.c --- src/modules/perl/mod_perl.c 25 Mar 2003 07:52:22 -0000 1.162 +++ src/modules/perl/mod_perl.c 2 Apr 2003 13:57:52 -0000 @@ -182,7 +182,7 @@

 #if defined(USE_REENTRANT_API) && defined(HAS_CRYPT_R) && defined(__GLIBC__)
     /* workaround perl5.8.0/glibc bug */
-    PL_reentrant_buffer->_crypt_struct.current_saltbits = 0;
+    PL_reentrant_buffer->_crypt_struct_buffer->current_saltbits = 0;
 #endif

     perl_run(perl);
Index: src/modules/perl/modperl_interp.c
===================================================================
RCS file: /home/cvspublic/modperl-2.0/src/modules/perl/modperl_interp.c,v
retrieving revision 1.57
diff -u -r1.57 modperl_interp.c
--- src/modules/perl/modperl_interp.c   27 Mar 2003 22:10:35 -0000      1.57
+++ src/modules/perl/modperl_interp.c   2 Apr 2003 13:57:53 -0000
@@ -67,7 +67,7 @@
         {
             dTHXa(interp->perl);
             /* workaround 5.8.0 bug */
-            PL_reentrant_buffer->_crypt_struct.current_saltbits = 0;
+            PL_reentrant_buffer->_crypt_struct_buffer->current_saltbits = 0;
         }
 #endif


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to