All of lore.kernel.org
 help / color / mirror / Atom feed
From: L A Walsh <lkml@tlinx.org>
To: util-linux@vger.kernel.org
Subject: ideas of what lib might be missing?  (2.29.2 has missing symbols @ link)
Date: Sat, 11 Mar 2017 04:41:08 -0800	[thread overview]
Message-ID: <58C3F064.4060904@tlinx.org> (raw)

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 )



             reply	other threads:[~2017-03-11 13:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-11 12:41 L A Walsh [this message]
2017-03-11 14:33 ` ideas of what lib might be missing? (2.29.2 has missing symbols @ link) J William Piggott
2017-03-11 22:50   ` L A Walsh
2017-03-13 11:41 ` Karel Zak
2017-03-14  2:03   ` L A Walsh
2017-03-14 10:16     ` Karel Zak

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=58C3F064.4060904@tlinx.org \
    --to=lkml@tlinx.org \
    --cc=util-linux@vger.kernel.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.