Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Andrei Dinu <andrei.adrianx.dinu@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] libpng : update to 1.60.0
Date: Sat, 02 Mar 2013 11:25:21 -0800	[thread overview]
Message-ID: <51325221.5050802@linux.intel.com> (raw)
In-Reply-To: <1361273568-30066-1-git-send-email-andrei.adrianx.dinu@intel.com>


While this is a straight forward patch, it causes some problems with 
depender's of libpng, since the library name changes from libpng15 -> 
libpng16 a lot of both -native and target packages fail to compile.

I know in the past we would do a load of PR bumps to all these packages 
to address this issue.

This is because many packages encode the libpng15 information into 
libtool (.la) files, when the sysroot is populated with an older build 
or sstate cache, the libpng15 info remains.

There already is a link from libpng.la, why does this not get used by 
libtool and stored in the .la file?

I am sure there is some strange magical history around this issue.

Thanks
Sau!


On 02/19/2013 03:32 AM, Andrei Dinu wrote:
> Signed-off-by: Andrei Dinu <andrei.adrianx.dinu@intel.com>
> ---
>   .../libpng/{libpng_1.5.14.bb => libpng_1.6.0.bb}   |   10 +++++-----
>   1 file changed, 5 insertions(+), 5 deletions(-)
>   rename meta/recipes-multimedia/libpng/{libpng_1.5.14.bb => libpng_1.6.0.bb} (50%)
>
> diff --git a/meta/recipes-multimedia/libpng/libpng_1.5.14.bb b/meta/recipes-multimedia/libpng/libpng_1.6.0.bb
> similarity index 50%
> rename from meta/recipes-multimedia/libpng/libpng_1.5.14.bb
> rename to meta/recipes-multimedia/libpng/libpng_1.6.0.bb
> index b2b82d3..951e34a 100644
> --- a/meta/recipes-multimedia/libpng/libpng_1.5.14.bb
> +++ b/meta/recipes-multimedia/libpng/libpng_1.6.0.bb
> @@ -3,17 +3,17 @@ DESCRIPTION = "PNG Library"
>   HOMEPAGE = "http://www.libpng.org/"
>   SECTION = "libs"
>   LICENSE = "Libpng"
> -LIC_FILES_CHKSUM = "file://LICENSE;md5=58c8238139ee86082f8d29eb89304241 \
> -                    file://png.h;beginline=207;endline=321;md5=4f17771edaee8bb3c17a95d7faaa3681"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=03b8ec701cb796c0ec84af22f884edef \
> +                    file://png.h;beginline=207;endline=321;md5=e829cebefd08488ba5142ea5faea6821"
>   DEPENDS = "zlib"
>   PR = "r0"
> -LIBV = "15"
> +LIBV = "16"
>
>   SRC_URI = "${SOURCEFORGE_MIRROR}/project/libpng/libpng${LIBV}/${PV}/libpng-${PV}.tar.xz \
>             "
>
> -SRC_URI[md5sum] = "94284b01d62ca43c5eb3f6702db08ed8"
> -SRC_URI[sha256sum] = "1459488e1b58d3be1c798453cf40c522c05bd66b61156cd51f469f17dff87b54"
> +SRC_URI[md5sum] = "3ee623b9a4d33bda7310a5124080b14d"
> +SRC_URI[sha256sum] = "5e13c31321083b03956b5ff298bacffab7a7ad35c34c122acef314593944b97b"
>
>   inherit autotools binconfig pkgconfig
>
>



  reply	other threads:[~2013-03-02 19:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-19 11:32 [PATCH] libpng : update to 1.60.0 Andrei Dinu
2013-03-02 19:25 ` Saul Wold [this message]
2013-03-02 19:33   ` Martin Jansa
2013-03-04 11:57   ` Burton, Ross

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=51325221.5050802@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=andrei.adrianx.dinu@intel.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