From: Andrei Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: configure.ac: Always add -D_FILE_OFFSET_BITS=64.
Date: Mon, 26 Jan 2015 19:50:50 +0300 [thread overview]
Message-ID: <20150126195050.13f6969a@opensuse.site> (raw)
In-Reply-To: <CAA91j0WFSjQiZ+W5vbv_JH39Qg92SRGdvR4m3eyWOsKdwtKOAA@mail.gmail.com>
В Mon, 26 Jan 2015 18:12:19 +0300
Andrei Borzenkov <arvidjaar@gmail.com> пишет:
> On Mon, Jan 26, 2015 at 6:04 PM, Vladimir 'φ-coder/phcoder' Serbinenko
> <phcoder@gmail.com> wrote:
> > On 26.01.2015 12:29, Andrei Borzenkov wrote:
> >>> +CPPFLAGS="$CPPFLAGS -D_FILE_OFFSET_BITS=64"
> >>> +HOST_CPPFLAGS="$HOST_CPPFLAGS -D_FILE_OFFSET_BITS=64"
> >>
> >>
> >> We already have them unconditionally in config.h. This is confusing;
> >> may be remove them from this file. OTOH we have AC_LARGEFILES that is
> >> expected to figure out proper options (although I believe for now
> >> there is just one system that needs it).
> >>
> > Do you mean AC_SYS_LARGEFILE ? Does it actually work?
>
> It apparently works for other projects ...
>
> > How exactly does
> > it make its way to HOST_CPPFLAGS?
>
> It does not, that is my point.
Sorry, was wrong. It makes it way via config-util.h
AC_CONFIG_HEADER([config-util.h])
and
/* Number of bits in a file offset, on hosts where this is settable. */
/* #undef _FILE_OFFSET_BITS */
/* Define for large files, on AIX-style hosts. */
/* #undef _LARGE_FILES */
I'm on 64 bit Linux so do not need any of these to enable large files.
So your patch seems to be redundant and I'd consider removing them from
config.h as well after release.
> We uncoditionally force both known
> knobs statically in config.h. I'm fine with forcing it in configure
> (then at least check for sizeof(off_t) will match what we have at
> compilation time) but then they must be removed from config.h.
>
> But yes, for now AC_SYS_LARGEFILE is pretty much useless here.
>
> >>
> >> This all looks rather messy.
> >>
> >> _______________________________________________
> >> Grub-devel mailing list
> >> Grub-devel@gnu.org
> >> https://lists.gnu.org/mailman/listinfo/grub-devel
> >>
> >
> >
> >
> > _______________________________________________
> > Grub-devel mailing list
> > Grub-devel@gnu.org
> > https://lists.gnu.org/mailman/listinfo/grub-devel
> >
next prev parent reply other threads:[~2015-01-26 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 11:29 configure.ac: Always add -D_FILE_OFFSET_BITS=64 Andrei Borzenkov
2015-01-26 15:04 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-01-26 15:12 ` Andrei Borzenkov
2015-01-26 16:50 ` Andrei Borzenkov [this message]
2015-01-27 16:28 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=20150126195050.13f6969a@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.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.