From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: xfs_io: fix test for fallocate on 32bit boxes
Date: Tue, 16 Jun 2009 10:04:54 -0500 [thread overview]
Message-ID: <4A37B496.2060403@sandeen.net> (raw)
In-Reply-To: <20090616140459.GA24783@infradead.org>
Christoph Hellwig wrote:
> On Mon, Jun 15, 2009 at 02:43:04PM -0500, Eric Sandeen wrote:
>> xfs_io: fix test for fallocate on 32bit boxes
>>
>> As per Red Hat bug 500487, fallocate64 is missing in glibc,
>> so attempts to build with fallocate and _FILE_OFFSET_BITS=64
>> will fail.
>>
>> So, change the config to test the way we will build, and
>> it'll fail properly on x86 until glibc gets fixed.
>
> Yikes. What's the status of actually getting it fixed in glibc?
> Otherwise we might have to switch to the raw syscall as ugly
> as it might be.
>
>From the bug:
Comment #6 From Jakub Jelinek (jakub@redhat.com) 2009-06-11 16:40:37 EDT
Unfortunately no, this can't be backported. The symbol is exported as
@@GLIBC_2.11 symbol, F11 has only glibc 2.10. If we add a single
GLIBC_2.11 symbol, we'd have to add them all, which means at least wait
until glibc 2.11 is released (in 4-5 months approximately).
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-06-16 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 19:43 xfs_io: fix test for fallocate on 32bit boxes Eric Sandeen
2009-06-15 20:12 ` Olaf Weber
2009-06-16 14:04 ` Christoph Hellwig
2009-06-16 15:04 ` Eric Sandeen [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=4A37B496.2060403@sandeen.net \
--to=sandeen@sandeen.net \
--cc=hch@infradead.org \
--cc=xfs@oss.sgi.com \
/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