From: Mike Westerhof <mike@mwester.net>
To: openembedded-devel@lists.openembedded.org
Subject: [PATCH] groff - fix do_install failure
Date: Wed, 23 Feb 2011 12:44:12 -0600 [thread overview]
Message-ID: <4D65557C.3020709@mwester.net> (raw)
Bitbaking groff fails in the do_install step, complaining that img/pic* does
not exist. Normally, these files would be created by groff itself during the
build process, but since we are cross-compiling, the old recipe replaces the
invocation of groff and troff with echo commands. However, echo does not
create the output files, which eventually results in the do_install failure.
This patch makes groff dependent on groff-native, and instead of using echo,
it instructs the build process to use the staged groff binaries.
Signed-off-by: Mike Westerhof <mike@mwester.net>
---
diff --git a/recipes/groff/groff_1.20.1.bb b/recipes/groff/groff_1.20.1.bb
index 6ea87dc..5869ff7 100644
--- a/recipes/groff/groff_1.20.1.bb
+++ b/recipes/groff/groff_1.20.1.bb
@@ -1,7 +1,10 @@
DESCRIPTION = "GNU roff"
SECTION = "base"
LICENSE = "GPL"
-PR = "r2"
+PR = "r3"
+
+DEPENDS = "groff-native"
+DEPENDS_virtclass-native = ""
SRC_URI = "http://ftp.gnu.org/gnu/groff/groff-${PV}.tar.gz \
"
@@ -15,10 +18,10 @@ PARALLEL_MAKE = ""
do_configure_prepend(){
if [ "${BUILD_SYS}" != "${HOST_SYS}" ]; then
sed -i \
- -e '/^GROFFBIN=/s:=.*:=echo:' \
- -e '/^TROFFBIN=/s:=.*:=echo:' \
- -e '/^GROFF_BIN_PATH=/s:=.*:=:' \
- -e '/^GROFF_BIN_DIR=/s:=.*:=:' \
+ -e '/^GROFFBIN=/s:=.*:=${STAGING_BINDIR_NATIVE}/groff:' \
+ -e '/^TROFFBIN=/s:=.*:=${STAGING_BINDIR_NATIVE}/troff:' \
+ -e '/^GROFF_BIN_PATH=/s:=.*:=${STAGING_BINDIR_NATIVE}:' \
+ -e '/^GROFF_BIN_DIR=/s:=.*:=${STAGING_BINDIR_NATIVE}:' \
${S}/contrib/*/Makefile.sub \
${S}/doc/Makefile.in \
${S}/doc/Makefile.sub
next reply other threads:[~2011-02-23 18:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 18:44 Mike Westerhof [this message]
2011-02-23 19:26 ` [PATCH] groff - fix do_install failure Khem Raj
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=4D65557C.3020709@mwester.net \
--to=mike@mwester.net \
--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.