From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH RFC] Add multilib values to displayed build configuration
Date: Thu, 6 Jun 2013 10:25:06 -0500 [thread overview]
Message-ID: <1370532307-14473-1-git-send-email-mark.hatle@windriver.com> (raw)
While attempting to help some users diagnose problems with multilib
configurations, I was tired of asking for copies of local.conf files and
dumps of the bitbake -e so I could understand how they had their multilib
environment setup. This is an attempt to add additional diagnostics to
the build configuration placed at the top of the logs.
I'm sending this as an RFC because it was a first quick and dirty attempt
at changing things. There may be a better way to do this.
Mark Hatle (1):
base.bbclass: Add buildcfg multilib values
meta/classes/base.bbclass | 16 +++++++++++++++-
meta/conf/bitbake.conf | 2 +-
2 files changed, 16 insertions(+), 2 deletions(-)
--
1.8.3.rc1.25.g423ecb0
next reply other threads:[~2013-06-06 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 15:25 Mark Hatle [this message]
2013-06-06 15:25 ` [PATCH RFC] base.bbclass: Add buildcfg multilib values Mark Hatle
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=1370532307-14473-1-git-send-email-mark.hatle@windriver.com \
--to=mark.hatle@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox