All of lore.kernel.org
 help / color / mirror / Atom feed
From: buysell08 <buysell08@benslade.com>
To: fio@vger.kernel.org
Subject: Getting 'stat64 already defined' type errors when trying to "make" fio on RedHat/Centos 6.3 (linux kernel 2.6.18-308)
Date: Fri, 30 Nov 2012 13:50:36 -0500	[thread overview]
Message-ID: <50B8FFFC.7000602@benslade.com> (raw)

I'm getting 'stat64 already defined' type errors when trying to "make" fio on RedHat/Centos 6.3 (linux kernel 2.6.18-308).

I couldn't find anything in the www.spinics.net/lists/fio mailing list archives about it.  Has anybody else seen a problem like this?

> make
DEP .depend
CC gettime.o
: Assembler messages:
:354: Error: symbol `fstatat64' is already defined
:388: Error: symbol `fstat64' is already defined
:418: Error: symbol `lstat64' is already defined
:448: Error: symbol `stat64' is already defined
:1704: Error: symbol `pread64' is already defined
make: *** [gettime.o] Error 1


Here's backgound version info from gcc:

> gcc -v
Reading specs from /usr/lib64/gcc-4.4.2/gcc/x86_64-unknown-linux-gnu/4.4.2/specs
Target: x86_64-unknown-linux-gnu
Configured with: ./configure --prefix=/usr/local/gcc/4.4.2 --enable-threads --enable-shared --enable-languages=c,c++ --disable-multilib --with-mpfr=/usr/local/gcc/4.4.2
--libdir=/usr/lib64/gcc-4.4.2 --with-include=/usr/local/gcc/4.4.2/include --with-gxx-include-dir=/usr/local/gcc/4.4.2/include/g++-v3
Thread model: posix
gcc version 4.4.2 (GCC)

> uname -r
2.6.18-308.8.1.el5

Thanks in advance
Ben

             reply	other threads:[~2012-11-30 18:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-30 18:50 buysell08 [this message]
2012-11-30 19:17 ` Getting 'stat64 already defined' type errors when trying to "make" fio on RedHat/Centos 6.3 (linux kernel 2.6.18-308) Jens Axboe
2012-12-02 19:20   ` Jens Axboe
2012-12-03 16:49     ` buysell08
2012-12-03 18:32       ` 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=50B8FFFC.7000602@benslade.com \
    --to=buysell08@benslade.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 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.