From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: [PATCH] bison: Use PATH to locate m4
Date: Mon, 18 Mar 2013 00:03:03 +0000 [thread overview]
Message-ID: <1363564983.4315.23.camel@ted> (raw)
We can specify no path to m4 at configure time and thus avoiding
having a wrapper for that particular problem.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
diff --git a/meta/recipes-devtools/bison/bison_2.7.bb b/meta/recipes-devtools/bison/bison_2.7.bb
index ee2effb..373651e 100644
--- a/meta/recipes-devtools/bison/bison_2.7.bb
+++ b/meta/recipes-devtools/bison/bison_2.7.bb
@@ -16,6 +16,9 @@ BASE_SRC_URI = "${GNU_MIRROR}/bison/bison-${PV}.tar.gz \
file://dont-depend-on-help2man.patch \
"
+# No point in hardcoding path to m4, just use PATH
+EXTRA_OECONF += "M4=m4"
+
SRC_URI = "${BASE_SRC_URI} \
file://fix_cross_manpage_building.patch \
"
@@ -32,8 +35,6 @@ acpaths = "-I ${S}/m4"
do_install_append_class-native() {
create_wrapper ${D}/${bindir}/bison \
- M4=${STAGING_BINDIR_NATIVE}/m4 \
BISON_PKGDATADIR=${STAGING_DATADIR_NATIVE}/bison
}
-#bison-native encodes the staging M4 path
BBCLASSEXTEND = "native nativesdk"
reply other threads:[~2013-03-18 0:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1363564983.4315.23.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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