[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 23:04:34 UTC 2016


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

--- Comment #24 from Mark Millard <markmi at dsl-only.net> ---
(In reply to w.schwarzenfeld from comment #23)

When I applied the new patch for 3.444 use to benchmarks/iozone in -r418253 of
/user/ports the messages were normal (see later below after I show the build
problem) but when I tried to build benchmarks/iozone it failed with problems
for applying patch-libasync.c :

===>  Found saved configuration for iozone-3.434
===>   iozone-3.444 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by iozone-3.444 for building
===>  Extracting for iozone-3.444
=> SHA256 Checksum OK for iozone3_444.tgz.
===>  Patching for iozone-3.444
===>  Applying FreeBSD patches for iozone-3.444
No such line 1217 in input file, ignoring
32 out of 33 hunks failed--saving rejects to libasync.c.rej
=> Patch patch-libasync.c failed to apply cleanly.
=> Patch(es) patch-iozone.c applied cleanly.
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/benchmarks/iozone
*** Error code 1

Stop.
make: stopped in /usr/ports/benchmarks/iozone

Your patch does not include anything for libasync.c and so leaves the older
patch-libasync.c in place.

FYI. . .

Applying your patch to -r418253 of /usr/ports and its benchmarks/iozone
reported:

Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|Index: Makefile
|===================================================================
|--- Makefile   (revision 418690)
|+++ Makefile   (working copy)
--------------------------
Patching file Makefile using Plan A...
Hunk #1 succeeded at 2 with fuzz 1.
Hunk #2 succeeded at 12.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|Index: distinfo
|===================================================================
|--- distinfo   (revision 418690)
|+++ distinfo   (working copy)
--------------------------
Patching file distinfo using Plan A...
Hunk #1 succeeded at 1.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|Index: files/patch-iozone.c
|===================================================================
|--- files/patch-iozone.c       (revision 418690)
|+++ files/patch-iozone.c       (working copy)
--------------------------
Patching file files/patch-iozone.c using Plan A...
Hunk #1 succeeded at 1.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|Index: files/patch-pit_server.c
|===================================================================
|--- files/patch-pit_server.c   (revision 418690)
|+++ files/patch-pit_server.c   (working copy)
--------------------------
Patching file files/patch-pit_server.c using Plan A...
Hunk #1 succeeded at 6.
done

(I cleaned out the 4 generated .orig files after this.)

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


More information about the freebsd-ports-bugs mailing list