All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dan Horák" <dan@danny.cz>
To: fio@vger.kernel.org
Subject: fio-2.0.12.2 doesn't build with ARCH_HAVE_CPU_CLOCK not defined
Date: Sun, 30 Dec 2012 23:11:51 +0100	[thread overview]
Message-ID: <1356905511.3343.24.camel@eagle.danny.cz> (raw)

Hi,

fio stopped to build on architectures that don't define
ARCH_HAVE_CPU_CLOCK like s390/s390x (fixed in a patch I've already
sent :-))

cc -o gettime.o -c -std=gnu99 -Wwrite-strings -Wall -O3 -g -O2 -g -pipe
-Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m31 -march=z9-109 -mtune=z10
-DFIO_VERSION='"fio-2.0.12.2"' -D_GNU_SOURCE -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_FORTIFY_SOURCE=2 -DFIO_INC_DEBUG gettime.c 
gettime.c: In function 'fio_clock_init':
gettime.c:317:6: error: 'tsc_reliable' undeclared (first use in this function)
gettime.c:317:6: note: each undeclared identifier is reported only once for each function it appears in
make: *** [gettime.o] Error 1

seems commit fa80feae51 added the tsc_reliable variable


	Thanks

		Dan



             reply	other threads:[~2012-12-30 22:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-30 22:11 Dan Horák [this message]
2013-01-01 10:00 ` fio-2.0.12.2 doesn't build with ARCH_HAVE_CPU_CLOCK not defined Jens Axboe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1356905511.3343.24.camel@eagle.danny.cz \
    --to=dan@danny.cz \
    --cc=fio@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.