[Freeciv-Dev] [bug #18872] Freeciv gives warnings with clang toolchain

Update of bug #18872 (project freeciv): Operating System: Mac OS => Any ___ Follow-up Comment #11: md5.c update in patch #4505, doesn't help with the clang compilation.

[Freeciv-Dev] [bug #18872] Freeciv gives warnings with clang toolchain

Follow-up Comment #10, bug #18872 (project freeciv): > Rats; that's the new MD5 code I pulled in for bug #18170. > Checking upstream finds no new version There has been some upstream updates last year, but I haven't checked if they fix this problem. Could jtn create patch for updating our codebas

[Freeciv-Dev] [bug #18872] Freeciv gives warnings with clang toolchain

Update of bug #18872 (project freeciv): Category:None => bootstrap Status:None => In Progress ___ Follow-up Comment #9: Somewhat related t

[Freeciv-Dev] [bug #18872] Freeciv gives warnings with clang toolchain

Follow-up Comment #8, bug #18872 (project freeciv): It's actually not my setup - it's a user of my Freeciv package in the 'fink' environment. But yeah, i'm fairly certain that he's on x86_64. I'll send him a new patch and see what happens. It won't happen right away though, as i've got some ca

[Freeciv-Dev] [bug #18872] Freeciv gives warnings with clang toolchain

Follow-up Comment #7, bug #18872 (project freeciv): Or we could just disable the optimisation -- we're only hashing passwords, not bulk data, so we hardly need it. ___ Reply to this item at: ___

[Freeciv-Dev] [bug #18872] Freeciv gives warnings with clang toolchain

Follow-up Comment #6, bug #18872 (project freeciv): > If so, we could avoid the warning by adding some sort of clang > detection in that #if. (Alternatively, by turning off > -Wcast-align for clang, but that's likely to be fiddlier and may > hide issues we're interested in.) The hyper proper way

[Freeciv-Dev] [bug #18872] Freeciv gives warnings with clang toolchain

Update of bug #18872 (project freeciv): Summary: Freeciv does not compile with clang => Freeciv gives warnings with clang toolchain ___ Follow-up Comment #5: Re the md5.c warning: I suspect it's running into this bit of c