From: Martin Jansa <martin.jansa@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-architecture
<openembedded-architecture@lists.openembedded.org>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [Openembedded-architecture] Cached size of off_t
Date: Thu, 14 Jan 2016 12:33:08 +0100 [thread overview]
Message-ID: <20160114113308.GB2582@jama> (raw)
In-Reply-To: <39606447-07D3-4F1F-93A1-CB9C77114535@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1940 bytes --]
On Tue, Jan 12, 2016 at 03:23:33PM -0800, Khem Raj wrote:
> Hi
>
> We cache size of off_t in site files and the value is 4 in most cases
>
>
> meta/site/arm-linux:ac_cv_sizeof_off_t=${ac_cv_sizeof_off_t=4}
> meta/site/ix86-common:ac_cv_sizeof_off_t=${ac_cv_sizeof_off_t=4}
> meta/site/nios2-linux:ac_cv_sizeof_off_t=${ac_cv_sizeof_off_t=4}
> meta/site/powerpc32-linux:ac_cv_sizeof_off_t=${ac_cv_sizeof_off_t=4}
> meta/site/x32-linux:ac_cv_sizeof_off_t=${ac_cv_sizeof_off_t=8}
> meta/site/x86_64-linux:ac_cv_sizeof_off_t=${ac_cv_sizeof_off_t=8}
>
>
> However this value is wrong when largefile support is enabled (which is default) on
> most OE based distros. It also lands us in nasty bugs which are complicated to uncover
> eg. the curl issue
>
> http://git.openembedded.org/openembedded-core/commit/?id=3c58712465494e441c4036a7cf21d2e6d343efab
>
> and just in OE-Core more e.g. grub2,libsndfile1,pax are showing same symptoms.
It's even more complicated in curl case, which bumps SONAME version when
off_t is changed.
So with dizzy we had libcurl5, but after the commit above we get
libcurl4 which looks strange considering the curl version in oe-core is newer now.
You can force the bump with --enable-soname-bump, but that doesn't make
it ABI compatible, because SIZEOF_OFF_T was really changed inside curl
build.
Regards,
> I think this value should be left for configure to compute and
> autotools.bbclass should pass --{enable|disable}-largefile based upon
> DISTRO_FEATURES enabling largefile support
>
> Do we see any downsides or point I might have missed
>
> Thank you
> -Khem
>
> _______________________________________________
> Openembedded-architecture mailing list
> Openembedded-architecture@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-architecture
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2016-01-14 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 23:23 Cached size of off_t Khem Raj
2016-01-13 0:09 ` [Openembedded-architecture] " Paul Eggleton
2016-01-13 0:19 ` Khem Raj
2016-01-13 0:22 ` Andre McCurdy
2016-01-13 9:00 ` Burton, Ross
2016-01-14 11:33 ` Martin Jansa [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=20160114113308.GB2582@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-architecture@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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