This is the mail archive of the crossgcc@cygnus.com mailing list for the crossgcc project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Everytime I try to build a gcc cross-compiler or a gcc native-comiler I have errors with include files, mostly stdio.h and ctypes.h. When I use /usr/include/*.h, then I get errors about variables in the header files (unknown opcode, statement syntax, invalid number of operands. These are probably not the right include files to be using, probably the ones that come with cc?? The include files found in newlib-1.8.1 don't work either, probably because they need to be build for the correct OS?? My ultimate goal is to build a DOS gcc cross-compiler for the M32R target. I have been trying to compile a cross compiler on a Sun workstation running Solaris2.6. gcc was installed when the OS was Solaris2.5. Then OS was updated to Solaris2.6. I seem to always have problems with include files. I am on the mailing list for crossgcc and gcchelp, I can't read newsgroups. One of these mail messages said something about rebuilding gcc if the OS has been updated since gcc was installed. I tried this and ran into snags, but got gcc built by switching between using gcc and cc to complete the build. However even after that I don't see new stdio.h and ctype.h files. So even using the new gcc, I still get missing header files when trying to build a i386-go32 gcc compiler on the sun. In another mail message someone said to run fixincludes if the OS was updated after the gcc was installed. I have not found good instructions on the operation of fixincludes, and I don't have permission to modify /usr/... files. Is this necessary? Please help. Thank you. ----------------------------------- John Taft Mitsubishi Electronic America, INC. 1050 East Arques Avenue Sunnyvale, California 94086-4601 DIRECT: 408-774-3262 MAIN: 408-730-5900 E_MAIL: jtaft@snv.mea.com -----------------------------------