Masaharu, I am converting existing code (written by someone else) to work with ROOT, rather than with Objectivity. The header file that this code included that caused the problem was <hash_map>. Apparently, it indirectly includes <bits/types.h>, although I have not traced the chain of #includes. In this particular case, I was able to avoid the #include of <hash_map> and work around the problem. I am, however, worried that next time that this happens there may be no obvious workaround. Bill Tanenbaum Masaharu Goto wrote: > > Hello Bill, > > I need to understand more about this situation. > > Basically, Cint goes with its own standard header files. > As long as those header files are used, there should be > no problem. Header files under /usr/include is used > only if designated header is not found among one goes > with Cint. So, it is not a problem that you see <bit/types.h> > in many of the /usr/include/* files. I guess you probably > include non standard header file and that causes the problem. > Let me look into Linux header file for gathering more information. > > Thank you > Masaharu Goto > > > > >Masaharu, > > This is just a simple example. Our code does not include > ><bits/types.h> directly. A quick grep of /usr/include shows that > ><bits/types.h> is directly #included in no fewer than 32 other header > >files in /usr/include. It is difficult to avoid it totally. > >It seems to me that this problem needs some attention. > > > >Bill Tanenbaum > > -- Bill Tanenbaum wmtan@fnal.gov (630)840-5228
This archive was generated by hypermail 2b29 : Sat Jan 04 2003 - 23:50:54 MET