From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Odd comment in openntpd/Config.in
Date: Mon, 6 Feb 2017 19:20:28 +0100 [thread overview]
Message-ID: <20170206192028.6b5ffae6@free-electrons.com> (raw)
In-Reply-To: <o7aan0$qvb$1@blaine.gmane.org>
Hello,
On Mon, 6 Feb 2017 17:10:56 +0000 (UTC), Grant Edwards wrote:
> In https://git.busybox.net/buildroot/tree/package/openntpd/Config.in:
>
> config BR2_PACKAGE_OPENNTPD
> bool "openntpd"
> depends on BR2_TOOLCHAIN_HAS_THREADS_NPTL
> [...]
>
> comment "openntpd needs a toolchain w/ NPTL"
> [...]
> depends on !BR2_TOOLCHAIN_HAS_THREADS_NPTL
>
> Is the "!" in the comment is a typo?
No, what you see is correct. We want the comment to show up when the
toolchain doesn't provide NPTL so that the user knows why openntpd is
not selectable.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-06 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 17:10 [Buildroot] Odd comment in openntpd/Config.in Grant Edwards
2017-02-06 18:13 ` Baruch Siach
2017-02-06 18:19 ` Grant Edwards
2017-02-06 18:20 ` Thomas Petazzoni [this message]
2017-02-06 18:21 ` Thomas Petazzoni
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=20170206192028.6b5ffae6@free-electrons.com \
--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