From: Phil Blundell <pb@pbcl.net>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: [PATCH] prelink: remove dependency on transfig-native
Date: Tue, 31 May 2011 12:29:04 +0100 [thread overview]
Message-ID: <1306841344.2525.484.camel@phil-desktop> (raw)
In-Reply-To: <1306405632.2525.306.camel@phil-desktop>
Per http://lists.linuxtogo.org/pipermail/openembedded-core/2011-May/003179.html
Signed-off-by: Phil Blundell <philb@gnu.org>
---
meta/recipes-devtools/prelink/prelink_git.bb | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/meta/recipes-devtools/prelink/prelink_git.bb
b/meta/recipes-devtools/prelink/prelink_git.bb
index 44aac2d..1eea30a 100644
--- a/meta/recipes-devtools/prelink/prelink_git.bb
+++ b/meta/recipes-devtools/prelink/prelink_git.bb
@@ -1,6 +1,7 @@
SECTION = "devel"
# Need binutils for libiberty.a
-DEPENDS = "elfutils binutils transfig-native"
+# Would need transfig-native for documentation if it wasn't disabled
+DEPENDS = "elfutils binutils"
SUMMARY = "An ELF prelinking utility"
DESCRIPTION = "The prelink package contains a utility which modifies
ELF shared libraries \
and executables, so that far fewer relocations need to be resolved at \
--
1.7.1
next prev parent reply other threads:[~2011-05-31 11:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 17:01 RDEPENDS_${PN} and virtclass-native Phil Blundell
2011-05-25 17:03 ` Chris Larson
2011-05-25 23:02 ` Richard Purdie
2011-05-25 23:08 ` Khem Raj
2011-05-26 10:15 ` Phil Blundell
2011-05-26 0:00 ` Richard Purdie
2011-05-26 0:11 ` Chris Larson
2011-05-26 0:59 ` Richard Purdie
2011-05-31 23:04 ` Richard Purdie
2011-05-26 10:27 ` Phil Blundell
2011-05-31 11:29 ` Phil Blundell [this message]
2011-05-31 11:46 ` [PATCH] prelink: remove dependency on transfig-native Richard Purdie
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=1306841344.2525.484.camel@phil-desktop \
--to=pb@pbcl.net \
--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