From: "S. Lockwood-Childs" <sjl@vctlabs.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][meta-filesystems][PATCH 1/2] libimobiledevice: remove runtime configure check
Date: Sat, 8 Aug 2015 17:30:37 -0700 [thread overview]
Message-ID: <20150809003037.GW8667@dent.vctlabs.com> (raw)
In-Reply-To: <60400991-1BCD-4AED-93C2-3C5DA77CE88A@gmail.com>
Apologies for managing to reply to the wrong thread the first time...
On Sat, Aug 08, 2015 at 04:01:38PM -0700, Khem Raj wrote:
>
> > On Jul 17, 2015, at 5:38 PM, S. Lockwood-Childs <sjl@vctlabs.com> wrote:
> >
> > configure.ac had a runtime check for large file support that got run
> > on 64-bit architectures, and all runtime checks must go away to be
> > cross-compile safe.
> >
> > Luckily that runtime check was extraneous, so just remove it;
> > standard AC_SYS_LARGEFILE macro should be sufficient for figuring out
> > proper settings to get large file support.
> >
> > Also un-blacklist libimobiledevice, since this problem was the
> > reason for the blacklist.
> >
>
> one difference is that now it will depend on --enable-largefile secondly, what does AC_SYS_LARGEFILE
> check do in the end ? is it a link time check ?
Not sure what you mean by 'now it will depend on --enable-largefile' since
the handling of that flag isn't being changed. I didn't add AC_SYS_LARGEFILE
macro; it was already there. The recipe still doesn't need to set that flag...
large file support should get enabled if the platform supports it.
AC_SYS_LARGEFILE does a compile-time check that off_t is large as expected,
and if not it tries some defines (such as _FILE_OFFSET_BITS) to see if they
can make off_t check pass. In the 64-bit Linux case, the first check passes,
since no tinkering with extra defines is needed, but for 32-bit case
_FILE_OFFSET_BITS will get defined.
next prev parent reply other threads:[~2015-08-09 0:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-18 0:38 [meta-oe][meta-filesystems][PATCH 1/2] libimobiledevice: remove runtime configure check S. Lockwood-Childs
2015-08-08 23:01 ` Khem Raj
2015-08-09 0:30 ` S. Lockwood-Childs [this message]
2015-10-01 15:06 ` Martin Jansa
2015-10-02 4:49 ` S. Lockwood-Childs
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=20150809003037.GW8667@dent.vctlabs.com \
--to=sjl@vctlabs.com \
--cc=openembedded-devel@lists.openembedded.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