From: Saul Wold <sgw@linux.intel.com>
To: Joe Slater <jslater@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] zlib: put shared libraries in base_libdir
Date: Wed, 15 May 2013 11:47:56 +0300 [thread overview]
Message-ID: <51934BBC.7010103@linux.intel.com> (raw)
In-Reply-To: <1368574528-28247-2-git-send-email-jslater@windriver.com>
On 05/15/2013 02:35 AM, Joe Slater wrote:
> We put the shared libraries in base_libdir because at least
> one library under base_libdir, pam_cracklib.so, needs them
> and will cause a qa warning when it is built.
> ---
> meta/recipes-core/zlib/zlib_1.2.7.bb | 14 ++++++++++++++
> 1 files changed, 14 insertions(+), 0 deletions(-)
>
> diff --git a/meta/recipes-core/zlib/zlib_1.2.7.bb b/meta/recipes-core/zlib/zlib_1.2.7.bb
> index 803fec3..f5deba1 100644
> --- a/meta/recipes-core/zlib/zlib_1.2.7.bb
> +++ b/meta/recipes-core/zlib/zlib_1.2.7.bb
> @@ -6,6 +6,8 @@ SECTION = "libs"
> LICENSE = "Zlib"
> LIC_FILES_CHKSUM = "file://zlib.h;beginline=4;endline=23;md5=94d1b5a40dadd127f3351471727e66a9"
>
> +PR = "r1"
> +
> SRC_URI = "http://www.zlib.net/${BPN}-${PV}.tar.bz2 \
> file://remove.ldconfig.call.patch \
> "
> @@ -22,6 +24,18 @@ do_compile (){
>
> do_install() {
> oe_runmake DESTDIR=${D} install
> +
> + # move the shared libraries to avoid possible qa warnings
> + #
> + case ${PN} in
> + zlib-native*)
> + ;;
This should really be handled by using the classing mechanism to extend
the do_install specificaly for the "target" class. The following will
append to the do_install for the target class.
do_install_append_class-target() {}
You should also protect against the case where base_libdir == libdir
which some distro can set.
I am also still investigating if this is an appropriate move from it's
default location, I guess I need to understand further why pam_cracklib
is causing a QA Warning, can you provide the warning please.
Thanks
Sau!
> + *)
> + mkdir -p ${D}/${base_libdir}
> + mv ${D}/${libdir}/libz.so.* ${D}/${base_libdir}
> + tmp=`readlink ${D}/${libdir}/libz.so`
> + ln -sf ../../${base_libdir}/$tmp ${D}/${libdir}/libz.so
> + esac
> }
>
> BBCLASSEXTEND = "native nativesdk"
>
next prev parent reply other threads:[~2013-05-15 9:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 23:35 [PATCH 0/1] zlib: put shared libraries under base_libdir Joe Slater
2013-05-14 23:35 ` [PATCH 1/1] zlib: put shared libraries in base_libdir Joe Slater
2013-05-15 8:47 ` Saul Wold [this message]
2013-05-15 9:54 ` Phil Blundell
2013-05-15 13:08 ` Mark Hatle
2013-05-15 19:50 ` Slater, Joseph
2013-05-15 20:44 ` Phil Blundell
2013-05-15 23:00 ` Slater, Joseph
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=51934BBC.7010103@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=jslater@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.