[uClibc]Duplicate macro defines and parse errors.

[Richard A. Smith]

On Wed, 17 Jan 2001 12:45:21 -0600 (CST), James Graves wrote:

>Tracing through the normal compilation of a program (such as PPPD) for
>my desktop OS (Debian 2.2r2) gives me a headache.  It is hard to tell
>which parts of include files are being used.

Amen... Its a PIA
>
>I've been thinking about writing a program that would trace out all
>the chains of includes, but haven't gotten around to it yet.  Copious
>free time and all that.

I think they already exist... I seem to remember seeing one somewhere. I was close to going 
and looking for it..

>I was under the impression that the bits/*.h stuff was to be used for
>user-space programs, and linux/*.h was for the kernel only.  But I'm
>really not sure.

That's what the the #warning statements say in the linux/*.h all say.. "Not to be included 
outside the kernel"


--
Richard A. Smith                         Bitworks, Inc.               
rsmith at bitworks.com               501.846.5777                        
Sr. Design Engineer        http://www.bitworks.com