From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gst-plugins-good: fix typo BR2_TOOLCHAIN_HAS_THREAD
Date: Fri, 20 Dec 2013 09:50:20 +0100 [thread overview]
Message-ID: <20131220095020.565215ee@skate> (raw)
In-Reply-To: <8ff8a1a8a7d5dfae8a57.1387486943@argentina>
Hello Yann,
On Thu, 19 Dec 2013 22:02:23 +0100, Thomas De Schampheleire wrote:
> comment "souphttpsrc needs a toolchain w/ wchar, threads"
> - depends on !BR2_USE_WCHAR || !BR2_TOOLCHAIN_HAS_THREAD
> + depends on !BR2_USE_WCHAR || !BR2_TOOLCHAIN_HAS_THREADS
Do you know if there is a way of making kconfig complain loudly if
there is a reference to an undefined symbol?
I know of only one occurrence in Buildroot where we rely on a
non-existing symbol: BR2_BROKEN. But we could just as well define this
symbol to be always false.
Having such a check would help ensuring we don't make typos on symbol
names.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-12-20 8:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 21:02 [Buildroot] [PATCH] gst-plugins-good: fix typo BR2_TOOLCHAIN_HAS_THREAD Thomas De Schampheleire
2013-12-19 21:32 ` Peter Korsgaard
2013-12-20 8:50 ` Thomas Petazzoni [this message]
2013-12-20 22:45 ` Yann E. MORIN
2013-12-21 8:39 ` Thomas Petazzoni
2013-12-21 13:10 ` Peter Korsgaard
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=20131220095020.565215ee@skate \
--to=thomas.petazzoni@free-electrons.com \
--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