Date: Wed, 20 Jul 2016 17:50:02 +0000
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 211152] benchmarks/iozone: Build fails on typedef redefinition with different types ('long long' vs '__off64_t' (aka 'long'))
Message-ID: <bug-211152-13-xfqNAX3XZ3@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-211152-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-211152-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=3D211152 --- Comment #42 from Mark Millard <markmi@dsl-only.net> --- Notes from Don Capps (the upstream owner) Most recent note: Revision 3.446 will appear on the Iozone web site within 24 hours.= =20=20 Slightly older material: The changes for : * FreeBSD handling of definition of __off_t=20 * Definition CACHE_LINE_SIZE changed to MY_CACHE_LINE_SIZE Have been merged into the official Iozone source tree and will appear in 3.445 and later releases. It is unclear how you wish to handle the printf and scanf issues that are related to long longs. It would be not be acceptable to change the format so that only more modern compilers would work. Many of the systems that compile and run Iozone span 2 decades of compilers. Breaking backwards compatibility would not be permitted. If you have a way to handle this without breaking previous builds, please send the diffs, and we'll put this in the queue of pending merges. I suspect that we may be doing a bunch of casting, so that we can maintain full backwards compatibility.=20=20 I'll note that 2016-20=3D=3D1996 so anything post-dating C89/C90 is unaccep= table for upstream. And anything not commonly implemented a few years after C89/C= 90 would also likely be unacceptable. --=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-211152-13-xfqNAX3XZ3>