[Lsb-infrastructure] devchk build fail with change

Wichmann, Mats D mats.d.wichmann at intel.com
Tue Jul 8 14:59:58 PDT 2008


after finally having applied the bug 2039 patch 3
stuff, the application battery is building through
cleanly.

One devchk check is now failing with the gcc build:

curses_h.c line 35:

CompareConstant(__NCURSES_H,1,2485,architecture,1.1,NULL)


This is an odd one; it's the protection constant present 
in the upstream header, it's one case where we need it 
purely for usefulness purposes - to protect against the
native ncurses.h header also being included - and not
for inclusion in the specification.  Perhaps this was
the one valid reason for Csrconly, but I bet we can
find some other way to express this situation.

In LSB we define this to have a value of 1, and this
the source of the generated check, but in the upstream
header it is not given a value and is only used as
an existence check:

#ifndef __NCURSES_H
#define __NCURSES_H


the other two curses ones that are questionable are
NCURSES_EXPORT and NCURSES_EXPORT_VAR, which aren't used
in the LSB context, but again are included only to
help compatibility with apps which may use the style
after having looked at ncurses headers....



More information about the lsb-infrastructure mailing list