rse 98/09/07 00:27:52
Modified: . STATUS
Log:
We need a little bit more time, because
1. the header/cpp stuff got more complicated than expected
2. the long-standing DSO/mod_perl problem is still not solved
because Doug's patch doesn't work under FreeBSD as expected.
Shit happens... so move the timeline to the date Brian requested...
Revision Changes Path
1.460 +31 -10 apache-1.3/STATUS
Index: STATUS
===================================================================
RCS file: /export/home/cvs/apache-1.3/STATUS,v
retrieving revision 1.459
retrieving revision 1.460
diff -u -r1.459 -r1.460
--- STATUS 1998/08/24 19:06:06 1.459
+++ STATUS 1998/09/07 07:27:51 1.460
@@ -2,7 +2,7 @@
Release:
- 1.3.2: In development. Release proposed for Monday, September 7th, 1998
+ 1.3.2: In development. Release proposed for Friday, September 18th, 1998
Ralf is volunteering as the release manager.
1.3.1: Tagged and rolled on July 19. Announced and released.
@@ -28,7 +28,14 @@
other includes first, etc. This breaks things like RLimit*
on many platforms.
- -- Ralf will try to solve this problem this week.
+ -- Ralf already hacked on this, but it's even more complicated
+ than we initially though. Because src/Configure has to check how CPP
+ can be called. On gcc systems that's gcc -E, on others there is a
cpp
+ in PATH. But on the remaining systems there is neither the canonical
+ -E nor cpp. I need more time for figuring out what's the best
+ approach. But currently I'm totally busy with mod_ssl and a
+ presentation I've to do on next Monday. I expect to finish this
+ before the 18th of September (1.3.2 release date).
-- Also, the return type of main is wrong in the test code and a
"test test" needs to be done to ensure we can be successful with
@@ -51,6 +58,23 @@
Available Patches:
+ * Patches for the DSO/mod_perl problem (see below for description):
+
+ Doug MacEachern's "[PATCH] fix for dso/mod_perl"
+ <[EMAIL PROTECTED]>
+ Status: Ralf -0 because it still doesn't work for me under FreeBSD.
+ We really have to find the real reason now. It's horrible
+ that only mod_perl is broken under DSO while other
+ module work. I really want to see mod_perl working
+ with DSO....
+
+ Ralf's "[PATCH] Fix module init"
+ This fixes the mod_so/mod_perl problems described under "FINAL RELEASE
+ SHOWSTOPPERS" by doing a more correct init of the modules after loading
+ through two new core API functions.
+ Message-ID: <[EMAIL PROTECTED]>
+ Status: Ralf +1, Lars +1
+
* Bill Stoddard's [PATCH] PR2356 - SSI exec
This is an update of a patch I sent in earlier. There are 13 new
lines of code to detect and handle shellcmd. COMMAND.COM is used
@@ -81,13 +105,6 @@
Message-Id: <[EMAIL PROTECTED]>
Status: Ken +1 (on concept), Lars +1 (on concept)
- * Ralf's "[PATCH] Fix module init"
- This fixes the mod_so/mod_perl problems described under "FINAL RELEASE
- SHOWSTOPPERS" by doing a more correct init of the modules after loading
- through two new core API functions.
- Message-ID: <[EMAIL PROTECTED]>
- Status: Ralf +1, Lars +1
-
* Paul's patch to add integrated restart/shutdown signalling (Win32)
This patch make Apache listen on predictable event names to allow
restarts and shutdowns to be initiated. Also adds a new command line
@@ -129,8 +146,12 @@
Currently at least mod_perl is broken under the DSO situation because
of
this missing init in mod_so. But perhaps there are more modules which
- have the same problem. This should be fixed for 1.3.1 or at least found
+ have the same problem. This should be fixed for 1.3.2 or at least found
out why it is happening!
+
+ Current status: We have two patches available (see above) but still
don't
+ know the real reason. And the patches work not under
+ all platforms :-(
* get_path_info bug; ap_get_remote_host should be ap_vformatter instead.
See: <[EMAIL PROTECTED]>
