From: "Diego Elio Pettenò" <flameeyes@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Re: RFC: Making largefile a global use
Date: Thu, 10 Mar 2011 11:49:34 +0100 [thread overview]
Message-ID: <1299754174.2212.62.camel@raven.home.flameeyes.eu> (raw)
In-Reply-To: <4D78A04F.3070206@gentoo.org>
Il giorno gio, 10/03/2011 alle 10.56 +0100, justin ha scritto:
>
>
> just because upstream has this configure flag. but it seems we agree
> on
> removing the flag completely, defaulting on largefile support and
> fixing
> what needs a fix.
> Correct?
Correct. Any configure with AC_SYS_LARGEFILE will get a
--enable-largefile option, but if you grep through the tree, this is
usually simply added unconditionally.
It is more interesting to see whether it actually supports LFS entirely;
quite a few packages forget to include config.h in some file or other,
and cause mixed LFS and non-LFS syscalls to be used, which is bad. I
have written an utility as part of Ruby-Elf[1] called verify-lfs that is
designed to check for that.
Also note that largefile has no meaning on most 64-bit arches (AMD64 for
sure, I guess the others as well).
[1] http://www.flameeyes.eu/projects/ruby-elf
--
Diego Elio Pettenò — Flameeyes
http://blog.flameeyes.eu/
next prev parent reply other threads:[~2011-03-10 10:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 8:08 [gentoo-dev] RFC: Making largefile a global use justin
2011-03-10 8:35 ` Mike Frysinger
2011-03-10 8:44 ` Dale
2011-03-10 20:12 ` Chris Richards
2011-03-10 8:36 ` Amadeusz Żołnowski
2011-03-10 8:42 ` justin
2011-03-10 9:34 ` Nirbheek Chauhan
2011-03-10 8:44 ` Mike Frysinger
2011-03-10 9:44 ` [gentoo-dev] " Diego Elio Pettenò
2011-03-10 9:56 ` justin
2011-03-10 10:49 ` Diego Elio Pettenò [this message]
2011-03-22 12:35 ` [gentoo-dev] " Peter Volkov
2011-03-22 13:59 ` Mike Frysinger
2011-03-10 17:52 ` [gentoo-dev] " Michał Górny
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=1299754174.2212.62.camel@raven.home.flameeyes.eu \
--to=flameeyes@gmail.com \
--cc=gentoo-dev@lists.gentoo.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