From: Mike Frysinger <vapier@gentoo.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: stephen.hemminger@vyatta.com, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] enable transparent LFS
Date: Wed, 27 May 2015 20:53:24 -0400 [thread overview]
Message-ID: <20150528005324.GD23204@vapier> (raw)
In-Reply-To: <20150527120726.65e9dd98@urahara>
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
On 27 May 2015 12:07, Stephen Hemminger wrote:
> On Tue, 26 May 2015 02:51:30 -0400
> Mike Frysinger <vapier@gentoo.org> wrote:
> > From: Mike Frysinger <vapier@chromium.org>
> >
> > Make sure we use 64-bit filesystem functions everywhere. This applies not
> > only to being able to read large files (which generally doesn't apply to
> > us), but also being able to simply stat them (as they might be using large
> > inodes).
> >
> > Signed-off-by: Mike Frysinger <vapier@chromium.org>
> > ---
> > Makefile | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/Makefile b/Makefile
> > index 35cacc4..9d35ef1 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -32,6 +32,8 @@ ADDLIB+=mpls_ntop.o mpls_pton.o
> > CC = gcc
> > HOSTCC = gcc
> > DEFINES += -D_GNU_SOURCE
> > +# Turn on transparent support for LFS
> > +DEFINES += -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
> > CCOPTS = -O2
> > WFLAGS := -Wall -Wstrict-prototypes -Wmissing-prototypes
> > WFLAGS += -Wmissing-declarations -Wold-style-definition -Wformat=2
>
> I am okay with this, is something specific it fixes or is it just
> general good practice?
general good practice at this point. we've started Gentoo down the path of
killing off non-LFS in projects.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-05-28 0:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 6:51 [PATCH iproute2] enable transparent LFS Mike Frysinger
2015-05-27 19:07 ` Stephen Hemminger
2015-05-28 0:53 ` Mike Frysinger [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=20150528005324.GD23204@vapier \
--to=vapier@gentoo.org \
--cc=netdev@vger.kernel.org \
--cc=stephen.hemminger@vyatta.com \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).