From: Allan Willems Joergensen <allan@nowhere.dk>
To: fio@vger.kernel.org
Subject: Compile error on IA64
Date: Tue, 15 Sep 2009 17:34:19 +0200 [thread overview]
Message-ID: <4AAFB3FB.5080404@nowhere.dk> (raw)
Hi,
I'm trying to compile fio on a Linux/IA64 machine; it fails.
# make
CC gettime.o
CC fio.o
CC ioengines.o
CC init.o
CC stat.o
CC log.o
CC time.o
CC filesetup.o
CC eta.o
CC verify.o
verify.c: In function `verify_async_init':
verify.c:896: warning: implicit declaration of function `write_barrier'
CC memory.o
CC io_u.o
CC parse.o
CC mutex.o
CC options.o
CC rbtree.o
CC diskutil.o
CC fifo.o
CC blktrace.o
CC smalloc.o
CC filehash.o
CC crc/crc7.o
CC crc/crc16.o
CC crc/crc32.o
CC crc/crc32c.o
CC crc/crc32c-intel.o
CC crc/crc64.o
CC crc/sha1.o
CC crc/sha256.o
CC crc/sha512.o
CC crc/md5.o
CC engines/cpu.o
CC engines/libaio.o
CC engines/mmap.o
CC engines/posixaio.o
CC engines/sg.o
CC engines/splice.o
CC engines/sync.o
CC engines/null.o
CC engines/net.o
CC engines/syslet-rw.o
CC engines/guasi.o
DEP depend
CC fio
verify.o(.text+0x52): In function `verify_async_exit':
/usr/local/src/fio/verify.c:907: undefined reference to `write_barrier'
verify.o(.text+0x7a2): In function `verify_async_init':
/usr/local/src/fio/verify.c:896: undefined reference to `write_barrier'
collect2: ld returned 1 exit status
make: *** [fio] Error 1
# uname -a
Linux xxxxxxxx 2.6.5-7.315-default #1 SMP Wed Nov 26 13:03:18 UTC 2008
ia64 ia64 ia64 GNU/Linux
# cat /etc/SuSE-release
SUSE LINUX Enterprise Server 9 (ia64)
VERSION = 9
PATCHLEVEL = 3
Any ideas? Am I missing something (devel package, library) or is it a
platform issue?
tia,
--
Med venlig hilsen / Best regards
Allan Willems Joergensen
"The weak die, the strong survive" - Toq
next reply other threads:[~2009-09-15 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 15:34 Allan Willems Joergensen [this message]
2009-09-15 17:54 ` Compile error on IA64 Jens Axboe
2009-09-15 18:03 ` Allan Willems Joergensen
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=4AAFB3FB.5080404@nowhere.dk \
--to=allan@nowhere.dk \
--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