[Lsb-messages] /var/www/bzr/lsb/devel/problem_db r310: Update #532 with new info (bug 3106, ncurses chtype mismatch).

Automatic Commit lsb-discuss at lists.linuxfoundation.org
Mon Aug 12 18:01:22 UTC 2013

revno: 310
author: licquia
committer: Automatic Commit <lsb-discuss at lists.linuxfoundation.org>
branch nick: problem_db
timestamp: Mon 2013-08-12 11:01:22 -0700
  Update #532 with new info (bug 3106, ncurses chtype mismatch).
-------------- next part --------------
=== modified file 'problem_db2'
--- a/problem_db2	2013-08-12 17:45:22 +0000
+++ b/problem_db2	2013-08-12 18:01:22 +0000
@@ -6818,8 +6818,9 @@
 TEST /olver/ncurses/terminal/tests/initscr_spec 1
   SEVERITY failed
    MARKER Segmentation fault: Invalid memory address
-COMMENT This issue is still under investigation
-LINK http://bugs.linuxbase.org/show_bug.cgi?id=3106 | bug 3106
+COMMENT Upstream ncurses defines the 'chtype' type as 'unsigned' without specifying int vs. long, but the LSB specification requires it to be 'long'.  This causes a problem on some 64-bit architectures.  The problem can be fixed in some cases by building ncurses using the --with-chtype=long configure flag.
+LINK http://bugs.linuxbase.org/show_bug.cgi?id=3106 | LSB bug 3106
+LINK https://bugs.mageia.org/show_bug.cgi?id=7235 | Mageia bug 7235
 RESOLUTION Known Problem

More information about the lsb-messages mailing list