Where would I pass this at? Not a programmer, poked around a little on google for it, and tried setting it in CFLAGS, but I still got the warning. Hobbit does indeed appear to work fine. It was just a curiosity.
Al
Al Jeffcoat
-----Original Message----- From: Henrik Stoerner [mailto:henrik at hswn.dk] Sent: Monday, June 27, 2005 5:10 PM To: hobbit at hswn.dk Subject: Re: [hobbit] Fedora Core 4 Install
On Mon, Jun 27, 2005 at 11:14:51AM -0400, Jeffcoat, Al wrote:
I'm getting the following warnings on an install of Hobbit onto Fedora Core 4, and wanted to find out if they are safe to ignore.
hobbitd.c: In function âhandle_statusâ: hobbitd.c:804: warning: pointer targets in passing argument 1 of âstrlenâ differ in signedness
I believe you can safely ignore those. Adding "-funsigned-char" to the compile-time options will probably eliminate them completely.
I'll do a test-install of FC4 to see if I can weed out those sometime.
(Being from a country where we depend on characters outside 7-bit ascii for just ordinary names does have some advantages - one of them being that I always assume chars to be unsigned. "-'q' ? You gotta be joking...")
Regards, Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
This e-mail message and any attached files are confidential and are intended solely for the use of the addressee(s) named above. If you are not the intended recipient, any review, use, or distribution of this e-mail message and any attached files is strictly prohibited. This communication may contain material protected by Federal privacy regulations, attorney-client work product, or other privileges. If you have received this confidential communication in error, please notify the sender immediately by reply e-mail message and permanently delete the original message. To reply to our email administrator directly, send an email to: postmaster at orlandoregional.org . If this e-mail message concerns a contract matter, be advised that no employee or agent is authorized to conclude any binding agreement on behalf of Orlando Regional Healthcare by e-mail without express written confirmation by an officer of the corporation. Any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of Orlando Regional Healthcare.
On Tue, Jun 28, 2005 at 10:24:51AM -0400, Jeffcoat, Al wrote:
Where would I pass this at? Not a programmer, poked around a little on google for it, and tried setting it in CFLAGS, but I still got the warning.
My guess was to add it in the top-level Makefile, near the bottom where it says
# Add local CFLAGS etc. settings here
CFLAGS += -funsigned-charThe Red Hat servers were busy when I tried picking up FC4 the other day, will try one of the mirrors later.
Hobbit does indeed appear to work fine. It was just a curiosity.
Oh, do report these kinds of things. Sometimes compiler really do catch errors I've made, and I always prefer the compile-phase to go "clean" without any warnings. Most people - myself included - do feel better about installing software that compiles without blasting tons of warnings across the screen.
Regards, Henrik
Henrik, If you like to get such informations, here is a short example, current source version 4.0.4
Compiler: cc: Compaq C V6.5-011 on Compaq Tru64 UNIX V5.1B (Rev. 2650) cxx: Compaq C V6.5-011 on Compaq Tru64 UNIX V5.1B (Rev. 2650)
cc: Warning: ../lib/sendmsg.c, line 316: In this statement, the referenced type of the pointer value "&connressize" is "unsigned long", which is not compatible with "int". (ptrmismatch) cc: Warning: contest.c, line 947: In this statement, the referenced type of the pointer value "&connressize" is "unsigned long", which is not compatible with "int". (ptrmismatch)
$ grep "cc: Warning" setup.log cc: Warning: digest.c, line 101: In this statement, the referenced type of the pointer value "&md_len" is "int", which is not compatible with "unsigned int" because they differ by signed/unsigned attribute. (ptrmismatch1) cc: Warning: encoding.c, line 31: In this statement, the referenced type of the pointer value "buf" is "unsigned char", which is not compatible with "const char" because they differ by signed/unsigned attribute. (ptrmismatch1) . . about 300 ptrmismatch1 warnings more, I can send you the whole input if you like a long mail :-)
Regards, Toni
Oh, do report these kinds of things. Sometimes compiler really do catch errors I've made, and I always prefer the compile-phase to go "clean" without any warnings. Most people - myself included - do feel better about installing software that compiles without blasting tons of warnings across the screen.
Regards, Henrik
participants (3)
-
Al.Jeffcoat＠orhs.org
-
anton.burkhalter＠gmx.net
-
henrik＠hswn.dk