should lsbcc use -nostdinc or not?

[Jeff Johnson]

+++ This bug was initially created as a clone of Bug #3714 +++

lsbcc is not using -nostdinc, but it probably should otherwise it may include
headers that are not part of LSB (such as argz.h):

$ cat >x.c <<EOF
#include <argz.h>
EOF
$ /opt/lsb/bin/lsbcc x.c -c
$ echo $?
0

$ /opt/lsb/bin/lsbcpp x.c
# 1 "x.c"
# 1 "<command-line>"
# 1 "x.c"
x.c:1:18: fatal error: argz.h: No such file or directory
compilation terminated.

$ /opt/lsb/bin/lsbcc x.c --lsb-verbose -c
cc -isystem /opt/lsb/include x.c -c -D__LSB_VERSION__=41 -fno-stack-protector
$ /opt/lsb/bin/lsbcpp x.c --lsb-verbose -c
cpp -nostdinc -I /opt/lsb/include -I /opt/lsb/include/c++ -c
-D__LSB_VERSION__=41 x.c

$ /opt/lsb/bin/lsbcc --lsbcc-version
/opt/lsb/bin/lsbcc (lsbcc) 4.1.18

$ /opt/lsb/bin/lsbcpp --lsbcc-version
/opt/lsb/bin/lsbcpp (lsbcc) 4.1.18

+++ end cloned information +++

To at least get to consistency beween parts, lsbcpp now behaves the same as
lsbcc, this is does NOT add -nostdinc to the modified command line.

However, some of the discussion in bug 3714 suggests maybe that's not the right
approach, so this bug is filed to track that question, which needs more
research.
[reply] [-] Comment 1