Shouldn't fixincludes remove assert.h instead of trying to fix it?

[Manfred Hollstein]

On Wed, 18 March 1998, 15:16:15, wilson@cygnus.com wrote:

    What happens if a file in /usr/include includes "assert.h" ?  What is
    something in /usr/include/sys includes "../assert.h"?  We don't want
    it to include the possibly broken /usr/include/assert.h.  We might have to
    have an assert.h file in the fixinclude directory just to avoid this problem.
    
    It doesn't necessarily have to be a fixed copy of the /usr/include/assert.h 
    file though.  It could be perhaps be gcc's assert.h file instead.  Changing
    where we install assert.h would require fixing some header file search 
    directory problems though.  For instance, TOOL_INCLUDE_DIR comes before
    GCC_INCLUDE_DIR when native but after cross, which means such a change may
    have undesirable side-effects that will need to be dealt with.
    
Why not simply install it in both directories?

manfred