From: Gary Thomas <gary@mlbassoc.com>
To: yocto discussion <yocto@yoctoproject.org>
Subject: perl 5.22 and 32 bit targets
Date: Wed, 23 Mar 2016 05:53:47 +0100 [thread overview]
Message-ID: <56F2215B.1000309@mlbassoc.com> (raw)
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.
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
------------------------------------------------------------
next reply other threads:[~2016-03-23 4:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 4:53 Gary Thomas [this message]
2016-03-23 5:36 ` perl 5.22 and 32 bit targets Khem Raj
2016-03-23 8:09 ` Gary Thomas
2016-03-23 8:40 ` Gary Thomas
2016-03-23 8:57 ` Jens Rehsack
2016-03-23 9:09 ` Gary Thomas
2016-03-23 9:14 ` Jens Rehsack
2016-03-23 9:48 ` Jens Rehsack
2016-03-23 11:00 ` Martin Jansa
2016-03-23 11:05 ` Gary Thomas
2016-03-23 11:43 ` Jens Rehsack
2016-03-23 12:07 ` Gary Thomas
2016-03-23 12:17 ` Jens Rehsack
2016-03-23 17:25 ` Gary Thomas
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=56F2215B.1000309@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=yocto@yoctoproject.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.