From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Alexander Dahl <ada@thorsis.com>,
Roland Hieber <rhi@pengutronix.de>,
Bruno Thomsen <bth@kamstrup.com>,
Mircea Ciocan <m.ciocan@ppc-ag.de>
Subject: [ptxdist] [PATCH] bc: prevent file name clash with busybox' bc
Date: Mon, 6 Jul 2020 15:21:02 +0200 [thread overview]
Message-ID: <20200706132100.10510-1-rhi@pengutronix.de> (raw)
In-Reply-To: <99644846.PknQacu39s@ada>
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
---
On Mon, Jul 06, 2020 at 03:19:06PM +0200, Alexander Dahl wrote:
> Would one of you care to send a patch?
I was just typing one up... :-)
- Roland
rules/bc.in | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/rules/bc.in b/rules/bc.in
index dabb244b5725..7095adc340b5 100644
--- a/rules/bc.in
+++ b/rules/bc.in
@@ -2,8 +2,12 @@
config BC
tristate
prompt "bc"
+ depends on !BUSYBOX_BC || ALLYES
help
bc is an arbitrary precision numeric processing language. Syntax is
similar to C, but differs in many substantial areas. It supports
interactive execution of statements. bc is a utility included in the
POSIX P1003.2/D11 draft standard.
+
+comment "busybox' bc is selected!"
+ depends on BUSYBOX_BS
--
2.27.0
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2020-07-06 13:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 13:09 [ptxdist] Clash between busybox bc and GNU bc Mircea Ciocan
2020-07-06 13:13 ` Bruno Thomsen
2020-07-06 13:19 ` Alexander Dahl
2020-07-06 13:21 ` Roland Hieber [this message]
2020-07-06 13:26 ` [ptxdist] [PATCH v2] bc: prevent file name clash with busybox' bc Roland Hieber
2020-07-07 5:45 ` [ptxdist] [APPLIED] " Michael Olbrich
2020-07-06 13:33 ` [ptxdist] [PATCH] " Alexander Dahl
2020-07-06 13:50 ` Roland Hieber
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=20200706132100.10510-1-rhi@pengutronix.de \
--to=rhi@pengutronix.de \
--cc=ada@thorsis.com \
--cc=bth@kamstrup.com \
--cc=m.ciocan@ppc-ag.de \
--cc=ptxdist@pengutronix.de \
/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