diff options
| author | Karel Zak | 2016-06-09 12:39:44 +0200 |
|---|---|---|
| committer | Karel Zak | 2016-06-09 12:39:44 +0200 |
| commit | 3d7cad18e79640dfd00e43ba4b789359c8469e8b (patch) | |
| tree | e280d8eb3e6947e806bbfc47ded8f41d7b3d444f /configure.ac | |
| parent | tests: fix for non-ncurses version (diff) | |
| download | kernel-qcow2-util-linux-3d7cad18e79640dfd00e43ba4b789359c8469e8b.tar.gz kernel-qcow2-util-linux-3d7cad18e79640dfd00e43ba4b789359c8469e8b.tar.xz kernel-qcow2-util-linux-3d7cad18e79640dfd00e43ba4b789359c8469e8b.zip | |
build-sys: remove global dependence between widechar and ncursesw
It seems that globally defined dependence between ncursesw and
wide-char support is overkill, because in some cases (e.g. cal(1)) we
can use ncurses independently on wide-char support.
It would be better to care about relation between wide-char and
ncurses individually (per util).
Signed-off-by: Karel Zak <kzak@redhat.com>
Diffstat (limited to 'configure.ac')
| -rw-r--r-- | configure.ac | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/configure.ac b/configure.ac index 2dbf592a0..f4d99f894 100644 --- a/configure.ac +++ b/configure.ac @@ -801,10 +801,6 @@ have_ncurses=no AS_CASE([$with_ncurses:$build_widechar], [yes:yes], [AC_MSG_ERROR([wide-char support enabled, but non-wide ncurses selects])]) -AS_CASE([$have_ncursesw:$with_ncurses:$build_widechar], - [no:auto:yes],[AC_MSG_WARN( [wide-char support enabled, ncursesw not found, force --without-ncurses]) - with_ncurses=no]) - AS_IF([test "x$have_ncursesw" = xno -a "x$with_ncurses" != xno ], [ PKG_CHECK_MODULES(NCURSES, [ncurses], [ have_ncurses=yes |