From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gpsd: needs threads
Date: Fri, 14 Dec 2012 11:35:58 +0100 [thread overview]
Message-ID: <876244kjjl.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1355480711-12089-1-git-send-email-gustavo@zacarias.com.ar> (Gustavo Zacarias's message of "Fri, 14 Dec 2012 07:25:11 -0300")
>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
Gustavo> Fixes
Gustavo> http://autobuild.buildroot.net/results/05925389ac2531307f23bf5f5f3a83a5a97301bf/
Gustavo> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
Gustavo> ---
Gustavo> package/gpsd/Config.in | 5 +++++
Gustavo> 1 files changed, 5 insertions(+), 0 deletions(-)
Gustavo> diff --git a/package/gpsd/Config.in b/package/gpsd/Config.in
Gustavo> index 69f63f9..35e535b 100644
Gustavo> --- a/package/gpsd/Config.in
Gustavo> +++ b/package/gpsd/Config.in
Gustavo> @@ -2,6 +2,7 @@ config BR2_PACKAGE_GPSD
Gustavo> bool "gpsd"
Gustavo> # Uses fork()
Gustavo> depends on BR2_USE_MMU
Gustavo> + depends on BR2_TOOLCHAIN_HAS_THREADS
Gustavo> help
Gustavo> gpsd is a service daemon that monitors one or more GPSes or AIS
Gustavo> receivers attached to a host computer through serial or USB ports,
Gustavo> @@ -12,6 +13,10 @@ config BR2_PACKAGE_GPSD
Gustavo> http://gpsd.berlios.de/
Gustavo> +
Gustavo> +comment "gpsd needs a toolchain with thread support"
Gustavo> + depends on !BR2_TOOLCHAIN_HAS_THREADS
Gustavo> +
Menuconfig has a bug which causes suboptions to not be indented if
there's a comment before them, so the comment needs to go either above
BR2_PACKAGE_GPSD or below all the sub options.
Committed with that fixed, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2012-12-14 10:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 10:25 [Buildroot] [PATCH] gpsd: needs threads Gustavo Zacarias
2012-12-14 10:35 ` Peter Korsgaard [this message]
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=876244kjjl.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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