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: Mon, 03 Dec 2012 19:32:07 +0100 [thread overview]
Message-ID: <50BCF027.5080503@kernel.dk> (raw)
In-Reply-To: <50BCD836.2040507@benslade.com>
On 2012-12-03 17:49, buysell08 wrote:
> Re: you write centos 6.3, but it's running kernel 2.6.18. That can't be right
>
> Indeed, it is not right. I meant to say Centos 6.3, kernel version
> 2.6.32. Apologies.
Did you change the compiler, too? gcc 4.4.2 isn't centos 6.3 stock
either.
> Re: Try adding a <sys/stat.h> include to fio.h
>
> No joy. Same compilation error
>
> But..... I found the web pages:
>
> http://mailman.videolan.org/pipermail/x264-devel/2011-June/008563.html
>
> http://lifecs.likai.org/2009/06/multiple-definition-of-extern-inline.html
>
> which says to add the compiler flag "-fgnu89-inline" (because of an issue where old glibc libraries aren't compatible with "the c99 standard"). I added the compilation flag
> (adding it just after the "-std=gnu99" option) and the compilation errors went away.
I found that that one, too. So you should be able to make it work by
just doing:
$ EXTFLAG="-std=gnu99" make
and not have to edit anything. Not sure I can do too much about this, if
it's a largely non-standard setup. It's a bug in your toolchain.
--
Jens Axboe
prev parent reply other threads:[~2012-12-03 18:32 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
2012-12-02 19:20 ` Jens Axboe
2012-12-03 16:49 ` buysell08
2012-12-03 18:32 ` Jens Axboe [this message]
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=50BCF027.5080503@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 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.