From: "Jeremy Lainé" <jeremy.laine@bolloretelecom.eu>
To: openembedded-devel@lists.openembedded.org
Subject: Re: klibc problems
Date: Thu, 02 Apr 2009 14:10:02 +0200 [thread overview]
Message-ID: <49D4AB1A.5060709@bolloretelecom.eu> (raw)
In-Reply-To: <49D488FC.3080803@xora.org.uk>
[-- Attachment #1: Type: text/plain, Size: 194 bytes --]
While we are on the topic, shouldn't the .so symlink get put in ${PN}-dev?
Attached is a patch that does just that.
--
Jeremy LAINE
Bolloré telecom | 11bis, rue Scribe | F-75009 Paris
[-- Attachment #2: klibc.diff --]
[-- Type: text/x-patch, Size: 1026 bytes --]
diff --git a/recipes/klibc/klibc.inc b/recipes/klibc/klibc.inc
index 15205c7..5fc9f52 100644
--- a/recipes/klibc/klibc.inc
+++ b/recipes/klibc/klibc.inc
@@ -59,7 +59,7 @@ do_stage() {
cp '${STAGING_DIR_TARGET}/bin/klcc' '${CROSS_DIR}/bin/${TARGET_PREFIX}klcc'
}
-PACKAGES = "${PN} klibc-utils-sh klibc-utils-kinit \
+PACKAGES = "${PN} ${PN}-dev klibc-utils-sh klibc-utils-kinit \
klibc-utils-fstype klibc-utils-ipconfig \
klibc-utils-nfsmount klibc-utils-resume \
klibc-utils-run-init klibc-utils-cat \
@@ -77,7 +77,8 @@ PACKAGES = "${PN} klibc-utils-sh klibc-utils-kinit \
klibc-utils-gzip klibc-utils-modprobe \
klibc-utils-losetup klibc-utils-wc"
-FILES_${PN} = "${base_libdir}/klibc*.so"
+FILES_${PN} = "${base_libdir}/klibc-*.so"
+FILES_${PN}-dev = "${base_libdir}/klibc.so"
FILES_klibc-utils-sh = "${base_bindir}/sh"
FILES_klibc-utils-gzip = "${base_bindir}/gzip ${base_bindir}/gunzip ${base_bindir}/zcat"
FILES_klibc-utils-kinit = "${base_bindir}/kinit"
next prev parent reply other threads:[~2009-04-02 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 12:03 klibc problems Graeme Gregory
2009-04-02 6:42 ` Khem Raj
2009-04-02 9:44 ` Graeme Gregory
2009-04-02 12:10 ` Jeremy Lainé [this message]
2009-04-21 9:18 ` Koen Kooi
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=49D4AB1A.5060709@bolloretelecom.eu \
--to=jeremy.laine@bolloretelecom.eu \
--cc=openembedded-devel@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