From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] Fix debug package generation in gcc-runtime
Date: Wed, 9 Mar 2011 17:52:42 -0600 [thread overview]
Message-ID: <cover.1299714512.git.mark.hatle@windriver.com> (raw)
The following patch fixes a the -dbg package generation for the gcc-runtime
packages. This is needed to enable debugging of C++ applications.
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: mhatle/bernard/fixes
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=mhatle/bernard/fixes
Thanks,
Mark Hatle <mark.hatle@windriver.com>
---
Mark Hatle (1):
gcc-runtime: Ensure that gcc-runtime builds a debug package
meta/recipes-devtools/gcc/gcc-package-runtime.inc | 3 +++
meta/recipes-devtools/gcc/gcc-runtime_4.5.1.bb | 2 +-
2 files changed, 4 insertions(+), 1 deletions(-)
--
1.7.3.4
WARNING: multiple messages have this Message-ID (diff)
From: Mark Hatle <mark.hatle@windriver.com>
To: <poky@lists.pokylinux.org>
Subject: [PATCH 0/1] Fix debug package generation in gcc-runtime
Date: Wed, 9 Mar 2011 17:50:50 -0600 [thread overview]
Message-ID: <cover.1299714512.git.mark.hatle@windriver.com> (raw)
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: mhatle/bernard/fixes
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=mhatle/bernard/fixes
Thanks,
Mark Hatle <mark.hatle@windriver.com>
---
Mark Hatle (1):
gcc-runtime: Ensure that gcc-runtime builds a debug package
meta/recipes-devtools/gcc/gcc-package-runtime.inc | 3 +++
meta/recipes-devtools/gcc/gcc-runtime_4.5.1.bb | 2 +-
2 files changed, 4 insertions(+), 1 deletions(-)
--
1.7.3.4
next reply other threads:[~2011-03-10 0:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 23:50 Mark Hatle [this message]
2011-03-09 23:52 ` [PATCH 0/1] Fix debug package generation in gcc-runtime Mark Hatle
2011-03-09 23:50 ` [PATCH 1/1] gcc-runtime: Ensure that gcc-runtime builds a debug package Mark Hatle
2011-03-09 23:52 ` 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=cover.1299714512.git.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 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.