Package Details: iozone 3.490-2

Git Clone URL: https://aur.archlinux.org/iozone.git (read-only, click to copy)
Package Base: iozone
Description: A filesystem benchmark tool
Upstream URL: http://www.iozone.org/
Licenses: custom
Submitter: sanerb
Maintainer: sanerb
Last Packager: sanerb
Votes: 28
Popularity: 0.46
First Submitted: 2015-08-25 00:00 (UTC)
Last Updated: 2021-01-14 21:55 (UTC)

Pinned Comments

sanerb commented on 2017-06-19 14:55 (UTC) (edited on 2017-09-01 22:56 (UTC) by sanerb)

# Bug reports can be filed at https://bugs.square-r00t.net/index.php?project=3 # News updates for packages can be followed at https://devblog.square-r00t.net (If you want an RSS-feed only pertaining to my AUR packages, you can subscribe to https://devblog.square-r00t.net/rss/?category=aur in your favourite RSS reader.) Note that you should still use the AUR web interface for flagging packages as out-of-date if a new version is released; the aforementioned bug tracker is to aid in issues with building/packaging/the PKGBUILD formats/etc. specifically. GPG signature "errors" are explained here: https://devblog.square-r00t.net/articles/a-note-on-using-gpg-signatures-in-pkgbuilds Please read; it's not a bug. Thanks!

Latest Comments

seblu commented on 2021-01-09 11:48 (UTC) (edited on 2021-01-09 11:48 (UTC) by seblu)

Hi Brent,

There is an issue with the package version. It should be forward or you have to bump epoch.

# pacman -Su
...
warning: iozone: local (3.490-2) is newer than seblu (3_490-1)

Regards,

sanerb commented on 2021-01-04 06:27 (UTC) (edited on 2021-01-04 06:39 (UTC) by sanerb)

@randyzhu-

yeah, looks like it's a gcc10 thing.

https://github.com/phoronix-test-suite/test-profiles/issues/139

i'll have a patch in place shortly.

EDIT: should be fixed, just needed a new CFLAG. i've confirmed it builds for me.

randyzhu commented on 2021-01-04 05:14 (UTC)

/usr/bin/ld: libbif.o:(.bss+0x8): multiple definition of `junk'; iozone_linux-AMD64.o:(.bss+0x340e0): first defined here
collect2: error: ld returned 1 exit status
make: *** [makefile:225: linux-AMD64] Error 1

Tried building in a clean chroot, doesn't seem to build for me.

Razathorn commented on 2020-12-23 20:04 (UTC)

I have been using this on my raspberry pi 4b (aarch64) on Manjaro today. Appears to work fine. Might consider adding aarch64 to the list of architectures.

sanerb commented on 2020-08-10 19:16 (UTC)

@shack thanks for testing and letting me know! done.

shack commented on 2020-08-09 21:09 (UTC)

Appears to build and run fine on Arch Linux ARM (armv7h). Please consider adding 'armv7h' to supported architectures in PKGBUILD.

sanerb commented on 2020-07-15 20:07 (UTC)

@chrisdunder-

D'oh. Thanks. I hate when they do that.

Problem avoided by just updating the package to 3.490. :)

Thanks for the heads-up!

chrisdunder commented on 2020-07-15 19:08 (UTC)

I'm getting checksum errors (sha512, not just pgp). Looks like a new version was released 2 days ago (version 490) and they also updated the 489 tar. Maybe they updated the 489 tar.

[   ]   iozone3_489.tar 13-Jul-2020 13:06   3.9M
[   ]   iozone3_490.tar 13-Jul-2020 13:27   3.9M

http://www.iozone.org/src/current/

bezirg commented on 2020-05-22 14:58 (UTC)

Out of date. 489 is the latest version

sanerb commented on 2019-03-09 19:59 (UTC)

@Velfess- see sticky.

Velfess commented on 2019-03-09 13:34 (UTC) (edited on 2019-03-09 13:35 (UTC) by Velfess)

Verifying source file signatures with gpg...
    iozone3_484.tar ... FAILED (unknown public key 8C004C2F93481F6B)
==> ERROR: One or more PGP signatures could not be verified!

sanerb commented on 2018-10-17 10:54 (UTC)

upstream updated, package updated, it indeed does now build correctly.

sanerb commented on 2018-10-16 18:37 (UTC)

per upstream, build has been fixed and new version (3.484) should be up within the next 24 hours.

sanerb commented on 2018-10-16 08:05 (UTC)

@deep_thought -

got your out-of-date notification. unfortunately, 3.483 gives the following error during build:

cc -c -O3 -Dunix -Dlinux -DHAVE_ANSIC_C -DASYNC_IO \
-D_LARGEFILE64_SOURCE -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt libasync.c  -o libasync.o 
libasync.c:1173:1: error: conflicting types for ‘async_write_no_copy’
 async_write_no_copy(struct cache *gc,long long fd,char *buffer,long long size,long long offset,long long depth,char *free_addr)
 ^~~~~~~~~~~~~~~~~~~
libasync.c:225:8: note: previous declaration of ‘async_write_no_copy’ was here
 size_t async_write_no_copy(struct cache *gc,long long fd,char *buffer,long long size,off64_t offset,long long depth,char *free_addr);
        ^~~~~~~~~~~~~~~~~~~
make: *** [makefile:1026: iozone_linux-AMD64.o] Error 1

so i'll need to pass it upstream. no 3.483 for now, i'm afraid.

sanerb commented on 2018-07-08 00:13 (UTC)

@applebloom-

terribly sorry! you are correct.

package fixed and bumped to most recent release (3.482). thanks!

applebloom commented on 2018-07-07 20:02 (UTC)

The install file refers in a message to a file, Guidelines.doc (supposedly it should be in /usr/share/doc/iozone), that isn't installed (and is nowhere in the package).

sanerb commented on 2017-06-19 14:55 (UTC) (edited on 2017-09-01 22:56 (UTC) by sanerb)

# Bug reports can be filed at https://bugs.square-r00t.net/index.php?project=3 # News updates for packages can be followed at https://devblog.square-r00t.net (If you want an RSS-feed only pertaining to my AUR packages, you can subscribe to https://devblog.square-r00t.net/rss/?category=aur in your favourite RSS reader.) Note that you should still use the AUR web interface for flagging packages as out-of-date if a new version is released; the aforementioned bug tracker is to aid in issues with building/packaging/the PKGBUILD formats/etc. specifically. GPG signature "errors" are explained here: https://devblog.square-r00t.net/articles/a-note-on-using-gpg-signatures-in-pkgbuilds Please read; it's not a bug. Thanks!

sanerb commented on 2016-08-26 16:24 (UTC) (edited on 2016-08-26 16:33 (UTC) by sanerb)

@skrunc- hrmmmm. yeah it builds fine for me... couple questions for you. 1.) are you using an AUR helper (apacman, yaourt, etc.)? 2.) are you able to download a clean copy of the snapshot, untar it, cd into it, run makepkg --check (or just download the iozone3_434.tar file manually), and do (as the same user you're building the package as): gpg --verify iozone3_434.tar.sig iozone3_434.tar if: - 1.) above is false, and the above command returns "gpg: Good signature from..." on the second line of output, then the issue is somewhere in your makepkg configuration. - 1.) above is false and the above command returns a FAILURE, you may not have imported my key correctly ( https://devblog.square-r00t.net/articles/a-note-on-using-gpg-signatures-in-pkgbuilds ) - 1.) above is true, i'd start by checking your AUR helper's config. i know apacman supports importing keys automatically, i can't recall if yaourt does or not. they use their own user to build packages, from what i remember. i can try to get you more help once i know which helper you're using, if you are.

skrunc commented on 2016-08-26 16:01 (UTC) (edited on 2016-08-26 16:07 (UTC) by skrunc)

Hi sanerb, I've got a problem with building the version "iozone3_434". Error is FAILED (unknown public key 8C004C2F93481F6B) ERROR: One or more PGP signatures could not be verified! I did add your key to my local keyring but this error still persists. What am I missing out? Regards

sanerb commented on 2016-06-26 04:49 (UTC)

@graysky: sorry for the delay- laptop crash, etc. should be back up and running now. your fixes/cleanups look awesome. incorporated them and pushed. ----- Please note the following additions: # Bug reports can be filed at https://bugs.square-r00t.net/index.php?project=3 # News updates for packages can be followed at https://devblog.square-r00t.net (If you want an RSS-feed only pertaining to my AUR packages, you can subscribe to https://devblog.square-r00t.net/rss/?category=aur in your favourite RSS reader.) Note that you should still use the AUR web interface for flagging packages as out-of-date if a new version is released; the aforementioned bug tracker is to aid in issues with building/packaging/the PKGBUILD formats/etc. specifically. Thanks!

sanerb commented on 2016-06-03 19:29 (UTC)

thanks graysky; sorry for the delay in response. i should have this fixed this weekend with a bump

graysky commented on 2016-05-22 19:21 (UTC)

Thank you for maintaining. The package 3_434-2 does not provide the man page and others. I have proposed a change to the PKGBUILD that does: https://gist.github.com/graysky2/c9b9d9ca14e87fe4a4d091dfb1c4fffd