Remove all compiler warnings from MariaDB:

- Remove all current warnings
- Add flag 'abort on compiler error
- Add flags to get more compiler errors

Drizzle has already done this, so we should be able to get hints from their code
for some of the fixes and the compiler warning flags

MySQL has done a lot of work on that in 5.5/5.6

Most of the warnings comes from the included readline libary.

One of the first tasks should be to update ours (based on 5.2) to the latest
readline version (6.0). After that:
- Update it with our changes to the readline (mostly about getting rid of warnings) 
- Fix so that there is no warnings from readline
- Update MariaDB with the new fixed library
- Send a patch of the fixed warnings to the current maintainer of readline

updated time estimates to be more realistic

High Level Description modified.
--- /tmp/wklog.25.old.24523	2010-09-09 07:16:37.000000000 +0000
+++ /tmp/wklog.25.new.24523	2010-09-09 07:16:37.000000000 +0000
@@ -7,5 +7,5 @@
 Drizzle has already done this, so we should be able to get hints from their code
 for some of the fixes and the compiler warning flags
 
- 
+MySQL has done a lot of work on that in 5.5/5.6
 

Version updated.
--- /tmp/wklog.25.old.28825	2010-07-24 11:38:33.000000000 +0000
+++ /tmp/wklog.25.new.28825	2010-07-24 11:38:33.000000000 +0000
@@ -1 +1 @@
-Server-5.1
+Server-9.x

High-Level Specification modified.
--- /tmp/wklog.25.old.10351	2009-05-27 15:47:46.000000000 +0300
+++ /tmp/wklog.25.new.10351	2009-05-27 15:47:46.000000000 +0300
@@ -1 +1,9 @@
+Most of the warnings comes from the included readline libary.
+
+One of the first tasks should be to update ours (based on 5.2) to the latest
+readline version (6.0). After that:
+- Update it with our changes to the readline (mostly about getting rid of warnings) 
+- Fix so that there is no warnings from readline
+- Update MariaDB with the new fixed library
+- Send a patch of the fixed warnings to the current maintainer of readline