From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/8] multilib: Add support for compiling recipes against multiple ABIs
Date: Mon, 01 Aug 2011 17:30:10 +0100 [thread overview]
Message-ID: <1312216211.30326.537.camel@phil-desktop> (raw)
In-Reply-To: <e393d2644b26b14f2b3b4b8e12177644921076b9.1311716946.git.richard.purdie@linuxfoundation.org>
On Tue, 2011-07-26 at 22:53 +0100, Richard Purdie wrote:
> +MULTILIBS ??= "multilib:lib32"
> +BBCLASSEXTEND_append_pn-linux-libc-headers = " ${MULTILIBS}"
> +BBCLASSEXTEND_append_pn-eglibc-initial = " ${MULTILIBS}"
> +BBCLASSEXTEND_append_pn-eglibc = " ${MULTILIBS}"
> +BBCLASSEXTEND_append_pn-libgcc = " ${MULTILIBS}"
> +BBCLASSEXTEND_append_pn-gcc-runtime = " ${MULTILIBS}"
> +BBCLASSEXTEND_append_pn-libtool-cross = " ${MULTILIBS}"
> +BBCLASSEXTEND_append_pn-zlib = " ${MULTILIBS}"
> +BBCLASSEXTEND_append_pn-binutils-cross = " ${MULTILIBS}"
> +BBCLASSEXTEND_append_pn-gcc-cross-initial = " ${MULTILIBS}"
> +BBCLASSEXTEND_append_pn-gcc-cross-intermediate = " ${MULTILIBS}"
> +BBCLASSEXTEND_append_pn-gcc-cross = " ${MULTILIBS}"
> +BBCLASSEXTEND_append_pn-busybox = " ${MULTILIBS}"
> +BBCLASSEXTEND_append_pn-update-rc.d = " ${MULTILIBS}"
> +BBCLASSEXTEND_append_pn-util-linux = " ${MULTILIBS}"
> +BBCLASSEXTEND_append_pn-gettext = " ${MULTILIBS}"
> +BBCLASSEXTEND_append_pn-bash = " ${MULTILIBS}"
> +BBCLASSEXTEND_append_pn-ncurses = " ${MULTILIBS}"
> +BBCLASSEXTEND_append_pn-expat = " ${MULTILIBS}"
> +BBCLASSEXTEND_append_pn-eglibc-locale = " ${MULTILIBS}"
What's the significance of this set of package names? I couldn't
immediately spot an obvious reason why these particular recipes were
getting special treatment.
It seems particularly weird to have update-rc.d in there since that is
an allarch recipe and (one hopes) isn't going to change much under
multilib.
p.
next prev parent reply other threads:[~2011-08-01 16:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 21:53 [PATCH 0/8] Multilib core enablement patches Richard Purdie
2011-07-26 21:53 ` [PATCH 1/8] multilib: Add support for compiling recipes against multiple ABIs Richard Purdie
2011-08-01 16:30 ` Phil Blundell [this message]
2011-08-01 17:00 ` Richard Purdie
2011-07-26 21:53 ` [PATCH 2/8] lib/oe/util.py: Add MLPREFIX support to prune_suffix() Richard Purdie
2011-07-26 21:53 ` [PATCH 3/8] do_split_packages: revise for multilib case Richard Purdie
2011-07-26 21:53 ` [PATCH 4/8] eglibc: fix for multilib RPROVIDES issue Richard Purdie
2011-07-26 21:53 ` [PATCH 5/8] cmake.bbclass: add ${libdir}} for multilib case Richard Purdie
2011-07-26 21:53 ` [PATCH 6/8] linux-yocto: revise the dependency for multilib Richard Purdie
2011-07-26 21:53 ` [PATCH 7/8] distcc: fix makefile parameter order Richard Purdie
2011-07-26 21:53 ` [PATCH 8/8] RPM: multilib file class/color Richard Purdie
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=1312216211.30326.537.camel@phil-desktop \
--to=philb@gnu.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox