From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 1CA52E00920; Wed, 23 Mar 2016 01:09:59 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mail.analogue-micro.com (mail.analogue-micro.com [217.144.149.242]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id C646AE00863 for ; Wed, 23 Mar 2016 01:09:55 -0700 (PDT) Received: by mail.analogue-micro.com (Postfix, from userid 999) id 6768768A01A; Wed, 23 Mar 2016 08:09:54 +0000 (GMT) Received: from zeus.mlbassoc.com (unknown [10.8.0.2]) by mail.analogue-micro.com (Postfix) with ESMTP id AED7868A019; Wed, 23 Mar 2016 08:09:51 +0000 (GMT) Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by zeus.mlbassoc.com (Postfix) with ESMTP id 05FDB67400D0; Wed, 23 Mar 2016 09:09:50 +0100 (CET) To: Khem Raj References: <56F2215B.1000309@mlbassoc.com> From: Gary Thomas Message-ID: <56F24F4E.70607@mlbassoc.com> Date: Wed, 23 Mar 2016 09:09:50 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Cc: yocto discussion Subject: Re: perl 5.22 and 32 bit targets X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Mar 2016 08:09:59 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 2016-03-23 06:36, Khem Raj wrote: > On Tue, Mar 22, 2016 at 9:53 PM, Gary Thomas wrote: >> I hope this is the correct place to discuss this problem. It >> is all about a difference in behavior between a program built >> using bitbake/OE (only OE-core is needed) vs building the program >> on the target hardware itself. >> >> I've been struggling with this problem since perl was upgraded >> to version 5.22. I'm working on Amanda (Advanced Maryland Archive >> tool) which is written primarily in perl and uses swig interfaces >> to access native C functions. This code works great when using >> the previous perl (5.20.x) but fails on all 32 bit targets with >> perl 5.22 >> >> The interesting thing is that if I build Amanda on my target >> directly (using SDK tools), it works perfectly even with perl >> 5.22, so it seems that there is some [subtle] difference between >> building using bitbake/OE than when built on the self-hosted >> target. I've compared the builds and the only thing I could >> find (from the output of configure) is a difference in sizeof(off_t) >> Sadly, when I tried to adjust this in the OE build, it didn't >> make any difference, but perhaps I didn't make this change >> correctly or completely. > > do you have largefile support turned on ? if you do then it might > be detecting it wrongly during configure since we cache it to a > non-largefile case > > so try to add something like > > EXTRA_OECONF += "${@bb.utils.contains('DISTRO_FEATURES', 'largefile', > 'ac_cv_sizeof_off_t=8', '', d)}" > > while building perl or the affected program and see if that helps Thanks for the idea, but that didn't help. I also forced some CFLAGS to match, in particular: -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 but this didn't make any difference either. >> >> Anyway, I'm looking for some help to solve this. I've put >> all the relevant pieces and notes about the process at: >> https://github.com/GaryThomas/meta-amanda.git -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------