From: Fabrice Fontaine <fontaine.fabrice@gmail.com>
To: buildroot@buildroot.org
Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Subject: [Buildroot] [PATCH 1/1] package/gdbm: needs wchar
Date: Thu, 30 Sep 2021 07:55:29 +0200 [thread overview]
Message-ID: <20210930055529.1929991-1-fontaine.fabrice@gmail.com> (raw)
wchar is a mandatoy dependency since bump to version 1.21 in commit
60add404db424e2652673a7b6a3ba2bc80380b42 and
https://git.savannah.gnu.org/cgit/gdbm.git/commit/src/datconv.c?id=0019677be7b751eb2d9b7e9ab25994cb696c7822
datconv.c:18:10: fatal error: wctype.h: No such file or directory
18 | #include <wctype.h>
| ^~~~~~~~~~
Fixes:
- http://autobuild.buildroot.org/results/b35ccdf734a02f0866fba7d86d44a8b452601607
Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
---
package/gdbm/Config.in | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/package/gdbm/Config.in b/package/gdbm/Config.in
index debe5660d7..7c8fcc4e5a 100644
--- a/package/gdbm/Config.in
+++ b/package/gdbm/Config.in
@@ -1,8 +1,13 @@
config BR2_PACKAGE_GDBM
bool "gdbm"
depends on BR2_USE_MMU # fork()
+ depends on BR2_USE_WCHAR
help
GNU dbm is a set of database routines that use extensible
hashing. It works similar to the standard UNIX dbm routines.
https://www.gnu.org/software/gdbm/gdbm.html
+
+comment "gdbm needs a toolchain w/ wchar"
+ depends on BR2_USE_MMU
+ depends on !BR2_USE_WCHAR
--
2.33.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2021-09-30 5:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 5:55 Fabrice Fontaine [this message]
2021-10-03 8:21 ` [Buildroot] [PATCH 1/1] package/gdbm: needs wchar Yann E. MORIN
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=20210930055529.1929991-1-fontaine.fabrice@gmail.com \
--to=fontaine.fabrice@gmail.com \
--cc=buildroot@buildroot.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.