Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Subject: [PATCH 10/10] libffi: really populate -dev package
Date: Fri, 23 Sep 2011 23:46:41 +0400	[thread overview]
Message-ID: <1316807201-22623-10-git-send-email-dbaryshkov@gmail.com> (raw)
In-Reply-To: <1316807201-22623-1-git-send-email-dbaryshkov@gmail.com>

As per gcc PR 11147, libffi installs headers into a target dependent
place (/usr/lib/....). Include a rule to include those files into
libffi-dev package.

Reference: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11147

Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
---
 meta/recipes-gnome/libffi/libffi_3.0.9.bb |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/meta/recipes-gnome/libffi/libffi_3.0.9.bb b/meta/recipes-gnome/libffi/libffi_3.0.9.bb
index b6c7c13..0ea2284 100644
--- a/meta/recipes-gnome/libffi/libffi_3.0.9.bb
+++ b/meta/recipes-gnome/libffi/libffi_3.0.9.bb
@@ -7,10 +7,13 @@ library really only provides the lowest, machine dependent layer of a fully feat
 A layer must exist above `libffi' that handles type conversions for values passed between the two languages."
 SRC_URI = "ftp://sourceware.org/pub/libffi/${BPN}-${PV}.tar.gz"
 
+PR = "r1"
+
 SRC_URI[md5sum] = "1f300a7a7f975d4046f51c3022fa5ff1"
 SRC_URI[sha256sum] = "589d25152318bc780cd8919b14670793f4971d9838dab46ed38c32b3ee92c452"
 LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=fa09cb778aaba64dc9eac37ab7e4e5d8"
 inherit autotools
 
+FILES_${PN}-dev += "${libdir}/libffi-${PV}"
 BBCLASSEXTEND = "native"
-- 
1.7.2.5




  parent reply	other threads:[~2011-09-23 19:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-23 19:46 [PATCH 01/10] default-provider: also define a default provider for gconf-native Dmitry Eremin-Solenikov
2011-09-23 19:46 ` [PATCH 02/10] bitbake.conf: change ccache path to use MULTIMACH_HOST_SYS Dmitry Eremin-Solenikov
2011-09-23 19:46 ` [PATCH 03/10] bash-completion: new recipe Dmitry Eremin-Solenikov
2011-09-25  9:46   ` Richard Purdie
2011-09-23 19:46 ` [PATCH 04/10] dbus-glib: include bash-completion stuff Dmitry Eremin-Solenikov
2011-09-23 20:09   ` Otavio Salvador
2011-09-25 17:20     ` Richard Purdie
2011-09-25 17:34       ` Otavio Salvador
2011-09-25 17:44         ` Richard Purdie
2011-09-25 17:48         ` Anders Darander
2011-09-23 19:46 ` [PATCH 05/10] eglibc: fix packaging of some of nativesdk packages, V2 Dmitry Eremin-Solenikov
2011-09-25 17:22   ` Richard Purdie
2011-09-23 19:46 ` [PATCH 06/10] icecc-create-env-native: provide the script right in the tree Dmitry Eremin-Solenikov
2011-09-23 19:46 ` [PATCH 07/10] gcc: fix possible problems with nscd compilation during eglibc-nativesdk build Dmitry Eremin-Solenikov
2011-09-23 19:46 ` [PATCH 08/10] gcc: include libgcov.a into libgcc-dev package Dmitry Eremin-Solenikov
2011-09-23 19:46 ` [PATCH 09/10] gconf-dbus: packaging fixup Dmitry Eremin-Solenikov
2011-09-23 19:46 ` Dmitry Eremin-Solenikov [this message]
2011-09-26 12:11 ` [PATCH 01/10] default-provider: also define a default provider for gconf-native Dmitry Eremin-Solenikov
2011-09-26 12:41   ` 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=1316807201-22623-10-git-send-email-dbaryshkov@gmail.com \
    --to=dbaryshkov@gmail.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