From: Michael Opdenacker <michael.opdenacker@free-electrons.com>
To: fio mailing list <fio@vger.kernel.org>
Subject: Build issue on arm: undefined reference to `get_cpu_clock'
Date: Tue, 10 Aug 2010 14:11:24 +0200 [thread overview]
Message-ID: <4C6141EC.7060205@free-electrons.com> (raw)
Hello,
Though the arm platform seems to be supported, fio fails to build on the
arm platform. Other non Intel platforms should also be impacted.
gettime.o: In function `get_cycles_per_usec':
/home/ubuntu/.phoronix-test-suite/installed-tests/fio/fio-1.42/gettime.c:192:
undefined reference to `get_cpu_clock'
/home/ubuntu/.phoronix-test-suite/installed-tests/fio/fio-1.42/gettime.c:199:
undefined reference to `get_cpu_clock'
make: *** [fio] Error 1
Unlike in the fio_gettime, where there is an "#ifdef
ARCH_HAVE_CPU_CLOCK" statement around the calls to get_cpu_clock(),
there are other places where this function is used unconditionally.
The get_cpu_clock function is only defined in
arch/arch-ia64.h
arch/arch-x86.h
arch/arch-x86_64.h
How are other architectures supported? I don't understand fio can
support them without defining the get_cpu_clock() function.
I did my tests on version 1.42, but faced the same issues with the
latest git version.
Thank you in advance.
Cheers,
Michael.
--
Michael Opdenacker, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
+ 33 621 604 642
next reply other threads:[~2010-08-10 12:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 12:11 Michael Opdenacker [this message]
2010-08-10 18:04 ` Build issue on arm: undefined reference to `get_cpu_clock' Jens Axboe
2010-08-12 9:04 ` Michael Opdenacker
2010-08-12 11:49 ` Jens Axboe
2010-08-15 19:03 ` Jens Axboe
2010-08-16 12:59 ` Michael Opdenacker
2010-08-16 22:27 ` 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=4C6141EC.7060205@free-electrons.com \
--to=michael.opdenacker@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox