[syslog-ng] 2.0RC4 make warning on OS X 10.4.8 PPC G4

Mr. Brian Opitz mrbriano at ofarrell-mail.sandi.net
Wed Oct 25 20:30:49 CEST 2006


System is OS X 10.4.8, Xcode 2.4, PPC G4(2.7), configure --enable-debug --enable-dynamic-linking

I am seeing the following warnings during compiling 2.0RC4:


logmsg.c: In function 'log_msg_parse':
logmsg.c:149: warning: pointer targets in assignment differ in signedness
logmsg.c:212: warning: pointer targets in passing argument 2 of 'g_string_assign_len' differ in signedness
logmsg.c:214: warning: pointer targets in assignment differ in signedness
logmsg.c:232: warning: pointer targets in passing argument 1 of 'strlen' differ in signedness
logmsg.c:271: warning: pointer targets in passing argument 2 of 'g_string_assign_len' differ in signedness
logmsg.c:309: warning: pointer targets in assignment differ in signedness
logmsg.c:313: warning: pointer targets in assignment differ in signedness
logmsg.c:344: warning: pointer targets in assignment differ in signedness
logmsg.c:378: warning: pointer targets in assignment differ in signedness
logmsg.c:389: warning: pointer targets in assignment differ in signedness
logmsg.c:401: warning: pointer targets in assignment differ in signedness
logmsg.c:413: warning: pointer targets in assignment differ in signedness
logmsg.c:435: warning: pointer targets in assignment differ in signedness
logmsg.c:440: warning: pointer targets in assignment differ in signedness
logmsg.c:445: warning: pointer targets in passing argument 2 of 'g_string_assign_len' differ in signedness

and:

affile.c: In function 'affile_dd_init':
affile.c:456: warning: comparison is always false due to limited range of data type
affile.c:462: warning: comparison is always false due to limited range of data type

and:

afuser.c: In function 'afuser_dd_queue':
afuser.c:57: warning: implicit declaration of function 'getutent'
afuser.c:57: warning: assignment makes pointer from integer without a cast

and finally:

gsockaddr.c: In function 'g_accept':
gsockaddr.c:116: warning: pointer targets in passing argument 3 of 'accept' differ in signedness

Can these safely be ignored or is there something that needs to be changed to make them go away?

--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.balabit.hu/pipermail/syslog-ng/attachments/20061025/8df1b21a/attachment.html


More information about the syslog-ng mailing list