All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel-hacker@bennee.com
To: openembedded-devel@lists.openembedded.org
Cc: Alex Bennee <ajb@cbnl.com>
Subject: [PATCH 1/2] freetype: include perl-native dependancy
Date: Thu, 12 Aug 2010 16:35:35 +0100	[thread overview]
Message-ID: <1281627336-686-2-git-send-email-kernel-hacker@bennee.com> (raw)
In-Reply-To: <1281627336-686-1-git-send-email-kernel-hacker@bennee.com>

From: Alex Bennee <ajb@cbnl.com>

Freetype requires a native perl to build during it's configure step.
I'm unsure how it built before unless other uses had brought in
perl-native through another dependancy (our GTK setup is fairly
minimal).

Signed-off-by: Alex Bennee <ajb@cbnl.com>
---
 recipes/freetype/freetype_2.3.11.bb |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/recipes/freetype/freetype_2.3.11.bb b/recipes/freetype/freetype_2.3.11.bb
index 1474bb9..8d3ca63 100644
--- a/recipes/freetype/freetype_2.3.11.bb
+++ b/recipes/freetype/freetype_2.3.11.bb
@@ -11,12 +11,15 @@ SRC_URI = "\
 "
 S = "${WORKDIR}/freetype-${PV}"
 
+DEPENDS	     = "perl-native"
+
 inherit autotools pkgconfig binconfig
 
 LIBTOOL = "${HOST_SYS}-libtool"
 EXTRA_OEMAKE = "'LIBTOOL=${LIBTOOL}'"
 EXTRA_OECONF = "--without-zlib"
 
+
 do_configure() {
 	cd builds/unix
 	libtoolize --force --copy
-- 
1.7.2.1




  reply	other threads:[~2010-08-12 16:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-12 15:35 A few fixes (resend, hopefully not munged this time) kernel-hacker
2010-08-12 15:35 ` kernel-hacker [this message]
2010-08-12 17:04   ` [PATCH 1/2] freetype: include perl-native dependancy Tom Rini
2010-08-12 17:23     ` Alex Bennee
2010-08-12 18:57       ` Tom Rini
2010-08-12 15:35 ` [PATCH 2/2] recode: Fix configure step kernel-hacker
2010-08-12 17:05   ` Tom Rini

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=1281627336-686-2-git-send-email-kernel-hacker@bennee.com \
    --to=kernel-hacker@bennee.com \
    --cc=ajb@cbnl.com \
    --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.