MySQL Bugs: #2372: LSB MySQL Porting Notes: undefined termcap data symbols

Bug #2372	LSB MySQL Porting Notes: undefined termcap data symbols
Submitted:	13 Jan 2004 7:50	Modified:	28 Sep 2010 19:25
Reporter:	Lenz Grimmer	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: Compiling	Severity:	S3 (Non-critical)
Version:	4.0.14,5.1	OS:	Linux (Linux)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
Excerpt from an email from Mats Wichmann with notes of a build of
MySQL 4.0.14 on 
an LSB system:

http://freestandards.org/pipermail/lsb-appbat/2003-October/001036.html

[SNIP]
4. in readline/terminal.h, the assumption is made
that if __linux__ is true, then the termcap global
data symbols PC, BC and UP are available.  In the
LSB, these are not defined at compile time since
they are not in the source standard for curses,
although they are of course likely to be present
in the runtime libncurses - however the LSB says
in this circumstance they cannot be used.

These symbols are from a set that is distinct from
the curses library; ncurses contains a meger of
the curses and the termcap libraries.  THey should
be configure-tested, and possibly an alternative
selected if not present.
[SNIP]

How to repeat:
Try to perform a MySQL build on an LSB development platform

moved to a todo: WL#1449

Closing these individual bugs, we have

 - a patch to fix these problems as of a few years ago (bug#29274)
 - a new bug to create ongoing PB2 builds to ensure LSB correctness (bug#57078)

to replace them.