I thought 'configure' was supposed to test for what was present
and what was missing? Seems to have missed a few... :-(
In trying to make new release 2.29.2, I'm getting
several undefined symbols:
color_fdisable
color_scheme_fenable
color_sequence_from_colorname
colormode_or_err
colors_init
get_fd_tabsize
get_terminal_name
initproctitle
pager_redirect
parse_kmsg_recordsetproctitle
plymouth_command
string_to_bitarray
strnchr
strtimeval_iso
strtos32_or_err
strtou32_or_err
unhexmangle_to_buffer
---
Was wondering what library I might be missing? or why they
are being referenced when 'whatever library' they are in,
evidently isn't on my system... configure bug?
I just ran the existing configure with the options listed
further on down...
Thanks!
-linda
uname -a:
Linux Ishtar 4.10.1-Isht-Van #1 SMP PREEMPT Tue Feb 28 18:57:48 PST 2017
x86_64 GNU/Linux
gcc (SUSE Linux) 4.9.0
glibc:
Name : glibc
Version : 2.19
Release : 16.9.1
vendor openSuSE 13.2
options:
array enable=(
fs-paths-default
last libmount-support-mtab line
newgrp
reset
static-programs=mount sulogin-emergency-mount
vipw write
)
array disable=( assert nls pylibmount )
array with=( audit
bashcompletiondir=/usr/share/bash-completion
gnu-ld
readline
)
array without=( python )
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
