[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-modperl-cvs
Subject:    cvs commit: modperl-2.0 STATUS
From:       stas () apache ! org
Date:       2003-09-26 19:22:38
[Download RAW message or body]

stas        2003/09/26 12:22:38

  Modified:    .        STATUS
  Log:
  we want to enable PERL_DL_NONLAZY=1 when MP_MAINTAINER=1
  
  Revision  Changes    Path
  1.65      +16 -1     modperl-2.0/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /home/cvs/modperl-2.0/STATUS,v
  retrieving revision 1.64
  retrieving revision 1.65
  diff -u -u -r1.64 -r1.65
  --- STATUS	23 Sep 2003 20:36:43 -0000	1.64
  +++ STATUS	26 Sep 2003 19:22:38 -0000	1.65
  @@ -236,6 +236,21 @@
   Open Issues or Core Enhancements:
   ---------------------------------
   
  +* As mike chamberlain told me over irc, apr-ext/perlio was faling for
  +  him because of the modperl_perl_gensym not being resolved in
  +  APR/PerlIO.so. I didn't see that error since on linux by default
  +  symbols resolution is lazy and since that part of the api wasn't
  +  tested I did see the problem. On MacOSX the loading is RTLD_NOW
  +  (non-lazy) so it detects any missing symbols problems immediately.
  +
  +  Luckily DynaLoader allows us to force the non-lazy mode by setting
  +  an env var: PERL_DL_NONLAZY=1. We need to force this env variable on
  +  when building with MP_MAINTAINER=1. I suppose that it should be
  +  added to the autogenerated t/TEST and t/SMOKE. and to
  +  t/conf/modperl_extra.pl ($ENV{PERL_DL_NONLAZY}=1) so it affects the
  +  server-side as well as the client-side (normally env var aren't
  +  propogated to the server).
  +
   * gcc 3.3 (from cvs 2003-07-28) supports a new option:
     -Wdeclaration-after-statement, which we need to enable in the
     maintainer mode, to catch any declarations after statements, since
  
  
  
[prev in list] [next in list] [prev in thread] [next in thread]