Date: Mon, 18 Jul 2016 05:05:26 +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-FlLdC2xywv@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 #19 from Mark Millard <markmi@dsl-only.net> --- (In reply to w.schwarzenfeld from comment #18) The CACHE_LINE_SIZE issue is failed as a separate defect and you do not nee= d to deal with it for this defect. Just for your information if you care: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210857 reports: iozone.c:762:9: warning: 'CACHE_LINE_SIZE' macro redefined [-Wmacro-redefin= ed] #define CACHE_LINE_SIZE 32 ^ /usr/include/machine/param.h:109:9: note: previous definition is here #define CACHE_LINE_SIZE (1 << CACHE_LINE_SHIFT) ^ (The line number in FreeBSD's param.h is possibly machine-type specific.) FYI: # grep CACHE_LINE_SIZE /usr/include/machine/param.h * CACHE_LINE_SIZE is the compile-time maximum cache line size for an #define CACHE_LINE_SIZE (1 << CACHE_LINE_SHIFT) (Both amd64 and armv6 show this grep result.) If /usr/include/machine/param.h is (indirectly) included by the header file handling then there is likely a CACHE_LINE_SIZE macro definition present in FreeBSD based compiles for those architectures that have cache lines. I do not know what compile context you use but I've been using the system c= lang 3.8.0 from 11.0 (-STABLE these days). Other compilers or compiler vintages = may not necessarily report the redefinition by default. My /etc/make.conf has just: WANT_QT_VERBOSE_CONFIGURE=3D1 # DEFAULT_VERSIONS+=3Dperl5=3D5.22 WRKDIRPREFIX=3D/usr/obj/portswork WITH_DEBUG=3D WITH_DEBUG_FILES=3D MALLOC_PRODUCTION=3D If you care you could check your /usr/include/machine/param.h to see if it = has a CACHE_LINE_SIZE define. But, again, it is a separate submittal with distinct consequences/issues so= you may want to ignore the potential CACHE_LINE_SIZE notices from some types of contexts completely. --=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-FlLdC2xywv>