From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Mutltilib patch status
Date: Fri, 22 Jul 2011 19:05:58 +0100 [thread overview]
Message-ID: <1311357958.2344.160.camel@rex> (raw)
I'm not as far advanced as I'd like to have been with the multilib
patches today but I've posted out the current cleaned up patches I have
to give an idea of where things are heading. I appended them to the
previous three patches I sent out and believe those patches so far so
stand on their own merit.
The complete series of my cleanup work so far are available at:
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=rpurdie/ml3
and you can enable multilib with lines like:
require conf/multilib.conf
MULTILIBS = "multilib:lib32 multilib:lib64"
DEFAULTTUNE_virtclass-multilib-lib32 = "i586"
DEFAULTTUNE_virtclass-multilib-lib64 = "x86-64"
in local.conf.
I've completed the ia32 tune files, I have not handled arm/mips/powerpc
yet. I've used a slightly improved formatting from Mark's version and
included more information in the commit messages to help people
understand the changes.
I've included two of Paul's bitbake BBCLASSEXTEND fixes in the series
for completeness.
Cheers,
Richard
reply other threads:[~2011-07-22 18:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1311357958.2344.160.camel@rex \
--to=richard.purdie@linuxfoundation.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