Bug 21684

Summary: cproto chokes on some standard header files
Product: [Retired] Red Hat Linux Reporter: John Bollinger <jobollin>
Component: cprotoAssignee: Bill Nottingham <notting>
Status: CLOSED DUPLICATE QA Contact: David Lawrence <dkl>
Severity: low Docs Contact:
Priority: medium    
Version: 6.2CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-12-04 16:24:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description John Bollinger 2000-12-04 16:24:42 UTC 
cproto reports numerous error messages when it processes some of the
standard C library
header files.  These files are processed because of their direct or
indirect inclusion in a
specified source file.  The errors occur without passing any options to
cproto, i.e.
"cproto *.c > protos".  cproto seems to successfully process the specified
source files
despite reporting dozens of parse errors in /usr/include/bits/types.h,
/usr/include/libio.h,
/usr/include/stdio.h, /usr/include/sys/types.h, /usr/include/fcntl.h, and
probably others.
Many, but not all, of the errors seemed to be related to internally defined
types, such as
__uid_t and __u_int.  I have assigned "low" severity to this bug because it
does not seem
to interfere with the program performing its function, but the multitude of
error messages is
likely to confuse and alarm some users.

I'm using cproto 4.6-3 and glibc-devel 2.1.3-19.
Comment 1 Bill Nottingham 2000-12-05 16:03:54 UTC 

*** This bug has been marked as a duplicate of 20535 ***