+1
> On Jun 21, 2016, at 3:07 PM, Kimmo Paasiala <kpaas...@gmail.com> wrote: > >> On Tue, Jun 21, 2016 at 9:32 PM, Doug Sampson <do...@dawnsign.com> wrote: >> Trying to rebuild iozone after a recent port upgrade and it crashes as >> follows: >> >> ### >> <...snip...> >> iozone.c:1297:1: error: unknown type name 'off64_t'; did you mean 'off_t'? >> off64_t offset = 0; /*offset for random I/O */ >> ^~~~~~~ >> off_t >> /usr/include/sys/types.h:173:18: note: 'off_t' declared here >> typedef __off_t off_t; /* file offset */ >> ^ >> iozone.c:1298:1: error: unknown type name 'off64_t'; did you mean 'off_t'? >> off64_t offset64 = 0; /*offset for random I/O */ >> ^~~~~~~ >> off_t >> /usr/include/sys/types.h:173:18: note: 'off_t' declared here >> typedef __off_t off_t; /* file offset */ >> ^ >> iozone.c:1299:1: error: unknown type name 'off64_t'; did you mean 'off_t'? >> off64_t filebytes64; >> ^~~~~~~ >> off_t >> /usr/include/sys/types.h:173:18: note: 'off_t' declared here >> typedef __off_t off_t; /* file offset */ >> ^ >> fatal error: too many errors emitted, stopping now [-ferror-limit=] >> 2 warnings and 20 errors generated. >> *** Error code 1 >> >> Stop. >> make[2]: stopped in /usr/ports/benchmarks/iozone/work/iozone3_434/src/current >> *** Error code 1 >> >> Stop. >> make[1]: stopped in /usr/ports/benchmarks/iozone >> *** Error code 1 >> >> Stop. >> make: stopped in /usr/ports/benchmarks/iozone >> root@pisces:/usr/ports/benchmarks/iozone# >> ### >> >> root@pisces:/usr/ports/benchmarks/iozone# make showconfig >> ===> The following configuration options are available for iozone-3.434: >> SSH=on: Use ssh in distributed measurement >> THREADS=on: Enable threading (uses pthreads) >> ===> Use 'make config' to modify these settings >> root@pisces:/usr/ports/benchmarks/iozone# >> >> Doesn't matter which config options I select/deselect, it still fails to >> rebuild. It occurs on both 10.3-RELEASE-p4 i386 and 10.3-RELEASE-p4 amd64 >> systems. >> >> >> ~Doug >> _______________________________________________ > > Same here on 10.3-RELEASE. I wonder how the port got updated with > sponsorship from "Gandi.net", yet the committed changes were > apparently not tested? Shouldn't Gandi.net volunteer as the maintainer > for the port if they want it to be updated (the port is unmaintained > at the moment)? > > -Kimmo > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" _______________________________________________ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"