All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [CONSOLIDATED PULL 04/18] libgcc: fix QA Packaging issues
Date: Fri, 28 Oct 2011 14:59:55 +0100	[thread overview]
Message-ID: <1319810395.3264.1.camel@ted> (raw)
In-Reply-To: <c69f8dfb51559661de1359f22a49f911c056d68e.1319753141.git.sgw@linux.intel.com>

On Fri, 2011-10-28 at 00:06 +0200, Saul Wold wrote:
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
> ---
>  meta/recipes-devtools/gcc/libgcc_4.6.bb |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
> 
> diff --git a/meta/recipes-devtools/gcc/libgcc_4.6.bb b/meta/recipes-devtools/gcc/libgcc_4.6.bb
> index 6ba0339..401d9dc 100644
> --- a/meta/recipes-devtools/gcc/libgcc_4.6.bb
> +++ b/meta/recipes-devtools/gcc/libgcc_4.6.bb
> @@ -6,6 +6,7 @@ DEPENDS = "virtual/${TARGET_PREFIX}gcc virtual/${TARGET_PREFIX}g++"
>  PACKAGES = "\
>    ${PN} \
>    ${PN}-dev \
> +  ${PN}-dbg \
>    "
>  
>  FILES_${PN} = "${base_libdir}/libgcc*.so.*"
> @@ -14,6 +15,7 @@ FILES_${PN}-dev = " \
>    ${libdir}/${TARGET_SYS}/${BINV}/crt* \
>    ${libdir}/${TARGET_SYS}/${BINV}/libgcov.a \
>    ${libdir}/${TARGET_SYS}/${BINV}/libgcc*"
> +FILES_${PN}-dbg = "${base_libdir}/.debug"

Isn't this second piece defined by default in bitbake.conf? I think we
can remove this second piece...

Cheers,

Richard




  reply	other threads:[~2011-10-28 14:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27 22:06 [CONSOLIDATED PULL 00/18] Patches, QA & Bug Fixes Saul Wold
2011-10-27 22:06 ` [CONSOLIDATED PULL 01/18] libtool: Upgrade from 2.4 -> 2.4.2 Saul Wold
2011-10-27 22:06 ` [CONSOLIDATED PULL 02/18] wget: Add recipe from OE Saul Wold
2011-10-27 22:06 ` [CONSOLIDATED PULL 03/18] dbus-glib: fix QA Packaging issues Saul Wold
2011-10-27 22:06 ` [CONSOLIDATED PULL 04/18] libgcc: " Saul Wold
2011-10-28 13:59   ` Richard Purdie [this message]
2011-10-27 22:06 ` [CONSOLIDATED PULL 05/18] at: " Saul Wold
2011-10-27 22:06 ` [CONSOLIDATED PULL 06/18] man: " Saul Wold
2011-10-27 22:06 ` [CONSOLIDATED PULL 07/18] mdadm: " Saul Wold
2011-10-27 22:06 ` [CONSOLIDATED PULL 08/18] libatomics-ops: " Saul Wold
2011-10-27 22:06 ` [CONSOLIDATED PULL 09/18] libproxy: " Saul Wold
2011-10-27 22:06 ` [CONSOLIDATED PULL 10/18] abiword: convert to svn Saul Wold
2011-10-27 22:06 ` [CONSOLIDATED PULL 11/18] dbus: remove unused initscript Saul Wold
2011-10-27 22:06 ` [CONSOLIDATED PULL 12/18] util-linux: split out mkfs into its own package Saul Wold
2011-10-27 22:06 ` [CONSOLIDATED PULL 13/18] e2fsprogs: move mke2fs.conf to e2fsprogs-mke2fs package Saul Wold
2011-10-27 22:06 ` [CONSOLIDATED PULL 14/18] distro_tracking_fields: update packages tracking fields Saul Wold
2011-10-27 22:06 ` [CONSOLIDATED PULL 15/18] documentation-audit.sh: script for auditing documentation build status Saul Wold
2011-10-27 22:06 ` [CONSOLIDATED PULL 16/18] avahi: use useradd to create user Saul Wold
2011-10-27 22:06 ` [CONSOLIDATED PULL 17/18] connman: create xuser Saul Wold
2011-10-27 22:06 ` [CONSOLIDATED PULL 18/18] xserver-nodm-init: use useradd to " Saul Wold
2011-10-28 14:16   ` Richard Purdie
2011-10-31 22:44 ` [CONSOLIDATED PULL 00/18] Patches, QA & Bug Fixes 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=1319810395.3264.1.camel@ted \
    --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 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.