Well the GCC 3.2 used on my Linux PPC reports also many warnings :-)
Making all in common
make[1]: Entering directory
`/root/jakarta-tomcat-connectors-1.2.10-src/jk/native/common'
/bin/sh /usr/share/apache2/build/libtool --silent --mode=compile gcc
-I/usr/include/apache2-prefork -g -O2 -O2 -fsigned-char -fPIC -Wall
-fno-strict-aliasing -D_LARGEFILE_SOURCE -g -Wmissing-prototypes
-Wstrict-prototypes -Wmissing-declarations -pthread -DHAVE_APR
-I/usr/include/apache2-prefork -g -O2 -DLINUX=2 -D_REENTRANT
-D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE
-DAP_DEBUG -I /usr/lib/jvm/java-1.4.2-ibm/include -I
/usr/lib/jvm/java-1.4.2-ibm/include/ -c jk_ajp12_worker.c
In file included from jk_uri_worker_map.h:35,
from jk_service.h:34,
from jk_ajp12_worker.h:27,
from jk_ajp12_worker.c:25:
jk_mt.h:81: warning: function declaration isn't a prototype
In file included from jk_uri_worker_map.h:36,
from jk_service.h:34,
from jk_ajp12_worker.h:27,
from jk_ajp12_worker.c:25:
jk_shm.h:91: warning: function declaration isn't a prototype
jk_shm.h:99: warning: function declaration isn't a prototype
jk_shm.h:118: warning: function declaration isn't a prototype
jk_shm.h:127: warning: function declaration isn't a prototype
jk_shm.h:134: warning: function declaration isn't a prototype
jk_shm.h:138: warning: function declaration isn't a prototype
jk_shm.h:141: warning: function declaration isn't a prototype
On Apr 1, 2005 4:06 PM, Jess Holle <[EMAIL PROTECTED]> wrote:
> Mladen Turk wrote:
>
> > Günter Knauf wrote:
> >
> >> Hi Mladen,
> >> Also I would like to mention that I'm probably way more frustrated
> >> about those banana patches than you cause I reported that compiler
> >> bug directly to the Novell manager who was reponsible for Metrowerks
> >> connection years ago, I even wrote a sample to demonstrate the
> >> problem; and after that three more versions of the stupid compiler
> >> were released and they from Metrowerks werre not able to fix it!!!!
> >
> Hmmmm.... Metrowerks used to be good back when I used it (early PowerPC
> Mac days).
>
> It was stricter than most compilers -- perhaps even causing some
> warnings to be errors. I understand how this can cause issues building
> open source software, but for my own development I always appreciated
> the compiler being stricter than others -- it made porting a lot
> easier. [I now use Java and am dismayed at what C compilers let you get
> away with.]
>
> --
> Jess Holle
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
