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] |
> > First, egcs requires certain system headers during the build. I copied > > those over from newlib, but it strikes me odd that egcs needed them when > > gcc-2.7.x didn't. > > Building 'libgcc.a', 'libobjc.a' and 'libg2c.a' would need some target > headers, not 'system' = 'native' headers... This is a 'chicken-and-egg' > problem and the easy way is to just copy the 'newlib/libc/include' to > the aimed install directory (e.g. '/usr/local/m68k-elf/include') where > the cross-compiler to be built will find them... Perhaps there is some > 'clean' way to solve this, but the 'quick-and-dirty' is usually the most > easy and you too seem to think this way... Another way that worked for me was to add --with-headers=../newlib-1.8.1/newlib/libc/include to the configure command for egcs. Then you end up with two sets of headers, one in /usr/local/<target>/sys-include immediately after the build of egcs and a second in /usr/local/<target>/include after building newlib. Eric ========================================================= To get command help for the crossgcc list, including help on adding/removing yourself to/from the list, send e-mail to majordomo@cygnus.com with the text 'help' (without the quotes) in the body of the message. =========================================================