Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: buysell08 <buysell08@benslade.com>
Cc: fio@vger.kernel.org
Subject: Re: 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 20:17:39 +0100	[thread overview]
Message-ID: <50B90653.2030808@kernel.dk> (raw)
In-Reply-To: <50B8FFFC.7000602@benslade.com>

On 2012-11-30 19:50, buysell08 wrote:
> 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

Never seen that before. From what I can tell on similar problems on
google, it's an issue with your glibc causing double definitions when
programs are compiled with _FILE_OFFSET_BITS= such as fio is.

If you can give me access to your system, I can probably add a
work-around for you.

-- 
Jens Axboe


  reply	other threads:[~2012-11-30 19:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-30 18:50 Getting 'stat64 already defined' type errors when trying to "make" fio on RedHat/Centos 6.3 (linux kernel 2.6.18-308) buysell08
2012-11-30 19:17 ` Jens Axboe [this message]
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=50B90653.2030808@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox