From: "Maxin B. John" <maxin.john@intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: [PATCH] gpsd: Fix build when static libs disabled
Date: Fri, 26 Feb 2016 12:02:27 +0200 [thread overview]
Message-ID: <1456480947-32277-1-git-send-email-maxin.john@intel.com> (raw)
Fix this build error:
SCons Error: no such option: --disable-static
Signed-off-by: Maxin B. John <maxin.john@intel.com>
---
meta-oe/recipes-navigation/gpsd/gpsd_3.14.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta-oe/recipes-navigation/gpsd/gpsd_3.14.bb b/meta-oe/recipes-navigation/gpsd/gpsd_3.14.bb
index ff268b3..a300595 100644
--- a/meta-oe/recipes-navigation/gpsd/gpsd_3.14.bb
+++ b/meta-oe/recipes-navigation/gpsd/gpsd_3.14.bb
@@ -47,6 +47,7 @@ EXTRA_OESCONS = " \
systemd='${SYSTEMD_OESCONS}' \
${EXTRA_OECONF} \
"
+DISABLE_STATIC = ""
# this cannot be used, because then chrpath is not found and only static lib is built
# target=${HOST_SYS}
--
2.4.0
next reply other threads:[~2016-02-26 9:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 10:02 Maxin B. John [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-01 8:12 [PATCH] gpsd: Fix build when static libs disabled Chris Trobridge
2016-03-01 4:14 ` [PATCH] gpsd: Fix build when static libs disabled Maxin B. John
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=1456480947-32277-1-git-send-email-maxin.john@intel.com \
--to=maxin.john@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox