From: Thomas Mueller <thomas@chaschperli.ch>
To: ceph-devel@lists.sourceforge.net
Subject: Re: build fails on centos 5
Date: Thu, 4 Mar 2010 15:47:54 +0000 (UTC) [thread overview]
Message-ID: <hmokna$lnv$2@dough.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.1003040707500.28379@cobra.newdream.net
Am Thu, 04 Mar 2010 07:11:00 -0800 schrieb Sage Weil:
> Hi Thomas,
>
> On Thu, 4 Mar 2010, Thomas Mueller wrote:
>> /usr/src/ceph-0.19.1/src/os/FileStore.cc:928: undefined reference to
>> `sync_file_range' libos.a(FileStore.o): In function
>> `FileStore::flusher_entry()':
>
> sync_file_range() appeared in 2.6.17. It sounds like CentOS 5 was based
> on an older kernel. Since your kernel is new, a recent glibc is
> probably all you need to get things going.
original centos kernel is 2.6.18. anyhow, i found a RHEL bug (which
centos is based on):
https://bugzilla.redhat.com/show_bug.cgi?id=518581
comment #1 from this bug:
It has only been added to glibc 2.6, and cannot be backported due to ABI
breakage. You can always fall back to syscall(3).
so, RHEL/CentOS 5 will never support this directly.
what about implementing the mentioned "syscall(3)" workaround for RHEL/
CentOS?
- Thomas
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
next prev parent reply other threads:[~2010-03-04 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 12:18 build fails on centos 5 Thomas Mueller
2010-03-04 15:11 ` Sage Weil
2010-03-04 15:47 ` Thomas Mueller [this message]
2010-03-04 16:18 ` Sage Weil
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='hmokna$lnv$2@dough.gmane.org' \
--to=thomas@chaschperli.ch \
--cc=ceph-devel@lists.sourceforge.net \
/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.