All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Cc: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
Subject: Re: [PATCH 2/3] freetype: build with system zlib
Date: Mon, 24 May 2010 19:39:48 -0400	[thread overview]
Message-ID: <20100524233948.GM25484@denix.org> (raw)
In-Reply-To: <13ca048a9b8e288c16467f1f833aeee6654d9981.1274642314.git.enrico.scholz@sigma-chemnitz.de>

On Sun, May 23, 2010 at 09:20:02PM +0200, Enrico Scholz wrote:
> Problems mentioned in 4187d3df8838506f6578a2b0f2fb98f98c41e151 (Aug
> 2006) seem to went away and build succeeds with system zlib now.  Using
> system libraries is preferable because it saves space and allows better
> tracking of security issues.
> 
> Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>

Acked-by: Denys Dmytriyenko <denis@denix.org>


> ---
>  recipes/freetype/freetype_2.3.12.bb |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/recipes/freetype/freetype_2.3.12.bb b/recipes/freetype/freetype_2.3.12.bb
> index de9ff29..b1f8d6f 100644
> --- a/recipes/freetype/freetype_2.3.12.bb
> +++ b/recipes/freetype/freetype_2.3.12.bb
> @@ -1,7 +1,8 @@
>  DESCRIPTION = "Freetype font rendering library"
>  SECTION = "libs"
>  LICENSE = "freetype"
> -PR = "r0"
> +PR = "r1"
> +DEPENDS = "zlib"
>  
>  SRC_URI = "\
>    ${SOURCEFORGE_MIRROR}/freetype/freetype-${PV}.tar.bz2 \
> @@ -18,7 +19,6 @@ inherit autotools pkgconfig binconfig
>  
>  LIBTOOL = "${HOST_SYS}-libtool"
>  EXTRA_OEMAKE = "'LIBTOOL=${LIBTOOL}'"
> -EXTRA_OECONF = "--without-zlib"
>  
>  do_configure() {
>  	cd builds/unix
> -- 
> 1.7.0.1
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel



  parent reply	other threads:[~2010-05-24 23:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-23 19:20 [PATCH 1/3] freetype: updated to 2.3.12 Enrico Scholz
2010-05-23 19:20 ` [PATCH 2/3] freetype: build with system zlib Enrico Scholz
2010-05-23 19:20   ` [PATCH 3/3] freetype: enable bytecode interpreter Enrico Scholz
2010-05-23 20:10     ` pieterg
2010-05-23 20:59       ` Enrico Scholz
2010-05-24 23:39   ` Denys Dmytriyenko [this message]
2010-05-24 23:39 ` [PATCH 1/3] freetype: updated to 2.3.12 Denys Dmytriyenko
2010-05-27 14:57 ` [PATCH (rebase) " Enrico Scholz
2010-05-27 14:57 ` [PATCH (rebase) 2/3] freetype: build with system zlib Enrico Scholz
2010-05-27 14:57 ` [PATCH (rebase) 3/3] freetype: enable bytecode interpreter Enrico Scholz

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=20100524233948.GM25484@denix.org \
    --to=denis@denix.org \
    --cc=enrico.scholz@sigma-chemnitz.de \
    --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 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.