From: Jesse Zhang <sen.zhang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH] [RFC] Perl packages shouldn't be allarch
Date: Tue, 19 Mar 2013 10:07:00 +0800 [thread overview]
Message-ID: <1363658821-23679-1-git-send-email-sen.zhang@windriver.com> (raw)
Hi,
I recently found that perl packages are broken in multilib builds. On a lib32
image, everything including perl is lib32 and installs to /usr/lib. These perl
packages are "all" arch, which is fine except that they install to /usr/lib64.
They won't work because the lib32 perl thinks its vendorlib is under /usr/lib.
Removing allarch seems to solve the problem, but I want to see if people have
some comments.
I found the original commit that introduced the change, which was to fix an
sstate related issue (https://bugzilla.yoctoproject.org/show_bug.cgi?id=1075).
But I don't think these packages fit well with allarch, since they install into
arch-specific dirs.
jesse
Jesse Zhang (1):
Perl packages shouldn't be allarch
meta/recipes-extended/perl/libconvert-asn1-perl_0.26.bb | 2 +-
meta/recipes-extended/perl/libtimedate-perl_2.30.bb | 2 +-
meta/recipes-extended/perl/libxml-namespacesupport-perl_1.11.bb | 2 +-
meta/recipes-extended/perl/libxml-sax-base-perl_1.08.bb | 2 +-
meta/recipes-extended/perl/libxml-sax-perl_0.99.bb | 2 +-
5 files changed, 5 insertions(+), 5 deletions(-)
--
1.7.11.7
next reply other threads:[~2013-03-19 3:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 2:07 Jesse Zhang [this message]
2013-03-19 2:07 ` [PATCH] Perl packages shouldn't be allarch Jesse Zhang
2013-03-25 2:03 ` [PATCH] [RFC] " Jesse Zhang
2013-03-25 3:22 ` Jesse Zhang
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=1363658821-23679-1-git-send-email-sen.zhang@windriver.com \
--to=sen.zhang@windriver.com \
--cc=openembedded-core@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 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.