This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug target/17508] Bootstrap fails to find system headers: sys/m_types.h, sys/limits.h


------- Additional Comments From wilson at specifixinc dot com  2004-09-15 22:13 -------
Subject: Re:  New: Bootstrap fails to find system headers:
 sys/m_types.h, sys/limits.h

skunk at iskunk dot org wrote:
> In file included from ./include/stdio.h:377,
>                  from /mnt/gnu/src/gcc/current/gcc/tsystem.h:79,
>                  from /mnt/gnu/src/gcc/current/gcc/libgcc2.c:41:
> ./include/sys/types.h:414:67: /mnt/gnu/arch/aix/include/sys/m_types.h: Missing
> file or filesystem

This looks like it could be a latent bug in the OS header files being 
triggered by fixincludes.  /usr/include/sys/types.h presumably has 
something like
     #include "m_types.h"
instead of the expected
     #include <sys/m_types.h>

Fixincludes then copies and fixes /usr/include/sys/types.h, but does not 
touch /usr/include/sys/m_types.h.  Now when the <sys/types.h> file is 
used, the m_types.h file can not be found.

This is something that we have to manually work around in fixincludes 
when we find examples of it.  We can either force the m_types.h file to 
be copied so it will be found, or use sed to fix the sys/types.h header 
file to use the correct include syntax.

Likewise for all of the other examples.

This can probably only be fixed by someone with access to the OS, and 
there probably aren't very many gcc developers with access to this target.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17508


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]