Date: Tue, 14 Feb 2017 20:08:39 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 217054] [patch] dns/void-zones-tools: update to e38ba1e (adds ARM support) Message-ID: <bug-217054-13-7rP1jI5wH9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-217054-13@https.bugs.freebsd.org/bugzilla/> References: <bug-217054-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217054 cyclaero@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cyclaero@gmail.com --- Comment #4 from cyclaero@gmail.com --- (In reply to mikael.urankar from comment #1) Hi, I am the developer of the void-zones-tools. You asked: "... char are unsigned on arm, are you sure you need 'CFLAGS =3D $(CDEFS) -fsigned-char' on arm?" Strictly speaking, this not necessary. However, my development environment is on a x86 system on which char is sig= ned by default. When I ported my software to arm, I ran into an issue within one quite old function of thousands, where I lazily assumed that char is always signed, as you said, it is not on ARM and not on other architectures. In addition, I got some other projects utilizing the same set of helper functions, which I want to work the same on every supported system. I revis= ited most of my code and it should be agnostic to the signedness of char. Anyway= , I find it important that all the standard C-types are behaving the smae on all the system that I want to support. So, I would have either added -funsigned-char for x86 or -fsigned-char for ARM, the latter of which was m= uch more effortless, and that's why I would like to aak to keep this as it is. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-217054-13-7rP1jI5wH9>