httpd-apreq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philippe M. Chiasson" <go...@cpan.org>
Subject Re: apreq-1 & apreq-2 status updates
Date Mon, 16 Jun 2003 02:08:41 GMT
On Sun, 2003-06-15 at 20:36, Joe Schaefer wrote:
> First the pending libapreq-1.2 release:
> 
>   a) I'm waiting for feedback from Stas on the
>      compile troubles he's run into on linux.
>      No rush, Stas-  but the output you posted
>      did look pretty scary ... :-/  In the future,
>      should we organize some regular smoke reports
>      for a few platforms?

./BUILD.sh && CFLAGS="-g3 -Wall" ./configure && make
On my RH9 builds fine with only one warning:
 apache_request.c:359: warning: `urlword_dlm' defined but not used

>   b) David Wheeler reports that the new test
>      suite is failing on OSX, although libapreq-1.2
>      seems to be working ok for him.  In lieu of a
>      working fix for the tests, I'd be happy to
>      apply a doc patch for README.MacOSX that
>      talks about this problem.
> 
>      btw- Can we get rid of that comment in the
>      BUGS section of Cookie.pm that talks about
>      Apache::Cookie not running on OSX?
> 
>   c) As I go through the release process, I'm working on
>      a draft RELEASE document in httpd-apreq cvs. I'm
>      writing it under the assumption that the RM
>      for libapreq has to be on the httpd PMC.
>      Eventually (post-release :-) we'll need to 
>      lay down sane guidelines for project releases 
>      which apply to both (apreq-1 & apreq-2) codebases.
>      The RELEASE document is just a first step in that
>      direction.
> 
> Second, wrt the httpd-apreq-2 cvs, I've patched the
> perl tests, added a build/doxygen.conf file and updated 
> Makefile.am accordingly.  Folks with doxygen installed
> should be able to build the C API docs by typing

./buildconf && CFLAGS="-g3 -Wall" ./configure && make 

Also is fine with a bit more warnings though:
apreq_params.c: In function `apreq_parse_request':
apreq_params.c:285: warning: unused variable `cfg'
apreq_parsers.c: In function `apreq_parse_multipart':
apreq_parsers.c:852: warning: suggest explicit braces to avoid ambiguous `else'
libapreq_cgi.c: In function `apreq_env_header_in':
libapreq_cgi.c:116: warning: implicit declaration of function `apr_toupper'
libapreq_cgi.c: In function `apreq_env_read':
libapreq_cgi.c:185: warning: implicit declaration of function `apreq_request_parse'
In file included from /home/gozer/opt/httpd/i386-linux/2.0.46-dev/worker/include/ap_config.h:269,
                 from /home/gozer/opt/httpd/i386-linux/2.0.46-dev/worker/include/httpd.h:72,
                 from mod_apreq.c:55:
/home/gozer/opt/httpd/i386-linux/2.0.46-dev/worker/include/ap_config_auto.h:161:1: warning:
"PACKAGE_BUGREPORT" redefined
mod_apreq.c:1:1: warning: this is the location of the previous definition
/home/gozer/opt/httpd/i386-linux/2.0.46-dev/worker/include/ap_config_auto.h:164:1: warning:
"PACKAGE_NAME" redefined
mod_apreq.c:1:1: warning: this is the location of the previous definition
/home/gozer/opt/httpd/i386-linux/2.0.46-dev/worker/include/ap_config_auto.h:167:1: warning:
"PACKAGE_STRING" redefined
mod_apreq.c:1:1: warning: this is the location of the previous definition
/home/gozer/opt/httpd/i386-linux/2.0.46-dev/worker/include/ap_config_auto.h:170:1: warning:
"PACKAGE_TARNAME" redefined
mod_apreq.c:1:1: warning: this is the location of the previous definition
/home/gozer/opt/httpd/i386-linux/2.0.46-dev/worker/include/ap_config_auto.h:173:1: warning:
"PACKAGE_VERSION" redefined
mod_apreq.c:1:1: warning: this is the location of the previous definition
In file included from /home/gozer/opt/httpd/i386-linux/2.0.46-dev/worker/include/ap_config.h:269,
                 from /home/gozer/opt/httpd/i386-linux/2.0.46-dev/worker/include/httpd.h:72,
                 from mod_apreq.c:55:
/home/gozer/opt/httpd/i386-linux/2.0.46-dev/worker/include/ap_config_auto.h:161:1: warning:
"PACKAGE_BUGREPORT" redefined
<command line>:1:1: warning: this is the location of the previous definition
/home/gozer/opt/httpd/i386-linux/2.0.46-dev/worker/include/ap_config_auto.h:164:1: warning:
"PACKAGE_NAME" redefined
<command line>:1:1: warning: this is the location of the previous definition
/home/gozer/opt/httpd/i386-linux/2.0.46-dev/worker/include/ap_config_auto.h:167:1: warning:
"PACKAGE_STRING" redefined
<command line>:1:1: warning: this is the location of the previous definition
/home/gozer/opt/httpd/i386-linux/2.0.46-dev/worker/include/ap_config_auto.h:170:1: warning:
"PACKAGE_TARNAME" redefined
<command line>:1:1: warning: this is the location of the previous definition
/home/gozer/opt/httpd/i386-linux/2.0.46-dev/worker/include/ap_config_auto.h:173:1: warning:
"PACKAGE_VERSION" redefined
<command line>:1:1: warning: this is the location of the previous definition
mod_apreq.c: In function `apreq_filter':
mod_apreq.c:387: warning: unused variable `f'
mod_apreq.c:324: warning: unused variable `saw_eos'

make perl_glue is fine

but make test fails because even though I provided the path to my apxs, when it builds the
httpd.conf, it parses
my config in /etc/httpd/* (RedHat). Don't know why exactly, but it ends up generating an invalid
httpd.conf for
my mostly static httpd...

>   % make docs
> 
> in the httpd-apreq-2 directory.  The generated
> html docs should wind up in the docs/html directory.

Nice!

> Doxygen is pretty cool!  Hopefully we'll have 
> similar luck with XSBuilder's pod generation stuff.
-- 
--------------------------------------------------------------------------------
Philippe M. Chiasson /gozer\@(cpan|ectoplasm)\.org/ 88C3A5A5 (122FF51B/C634E37B)
http://gozer.ectoplasm.org/    F9BF E0C2 480E 7680 1AE5 3631 CB32 A107 88C3 A5A5
Q: It is impossible to make anything foolproof because fools are so ingenious.
perl -e'$$=\${gozer};{$_=unpack(P7,pack(L,$$));/^JAm_pH\n$/&&print||$$++&&redo}'


Mime
View raw message