[Bug 211152] benchmarks/iozone: Build fails on typedef redefinition with different types ('long long' vs '__off64_t' (aka 'long'))

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Jul 18 05:05:26 UTC 2016


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211152

--- Comment #19 from Mark Millard <markmi at 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 need to
deal with it for this defect.

Just for your information if you care:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210857 reports:

iozone.c:762:9: warning: 'CACHE_LINE_SIZE' macro redefined [-Wmacro-redefined]
#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 clang
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=1
#
DEFAULT_VERSIONS+=perl5=5.22
WRKDIRPREFIX=/usr/obj/portswork
WITH_DEBUG=
WITH_DEBUG_FILES=
MALLOC_PRODUCTION=

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.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list