www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From traw...@apache.org
Subject Re: build/6980: Copious build warnings
Date Sat, 03 Mar 2001 02:33:32 GMT
[In order for any reply to be added to the PR database, you need]
[to include <apbugs@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]

Synopsis: Copious build warnings

State-Changed-From-To: analyzed-closed
State-Changed-By: trawick
State-Changed-When: Fri Mar  2 18:33:32 PST 2001
As much as practical has been fixed in the current CVS 
repositories for Apache and APR.  Some warnings not mentioned
in an earlier update had already been fixed.  Many more
warnings were fixed for this PR.

Here is a synopsis of what went in.  Warnings not related
to observable behavior were not mentioned in detail.  Some
code near or intertwined with code causing a warning was
found to be in error and was fixed.

RCS file: /home/cvs/httpd-2.0/CHANGES,v
retrieving revision 1.118
diff -u -r1.118 CHANGES
--- CHANGES	2001/03/02 22:46:30	1.118
+++ CHANGES	2001/03/03 02:25:08
@@ -1,5 +1,13 @@
 Changes with Apache 2.0.14-dev
+  *) Fix a number of SGI compile warnings throughout the server.  Fix some
+     bad parameters to apr_bucket_read().  Fix a bad statement in 
+     ap_method_in_list().  For the mod_rewrite cache use apr_time_t 
+     consistently; we were mixing apr_time_t and time_t in invalid ways 
+     before.  In load_file(), call apr_dso_error() instead of 
+     apr_strerror() so that we get a more specific string on some platforms.
+     PR #6980  [Jeff Trawick]

Hopefully a build of current code will be relatively clean,
especially after certain expected warnings (mentioned in a
previous update) are filtered out.

View raw message