This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Hi, I am compiling a crosscompiler with target powerpc-eabi. We have different target operatingsystems dilivered together with different versions of the diab compiler. To make a gcc cross compiler I first build and install binutils, and afterwards I build gcc. But here comes my problem. If I build the gcc compiler with option --with-headers=/path/to/diab/some/version/include everything goes OK, but if I omit that I get two compiler errors in the files: gcc/frame.c and in gcc/libgcc2.c. Thise errors can be removed if I define inhibit_libc in the beginning af the two files. If I use this method, which feature must I expect to miss in the compiler compared with the one where I have delivered some system libraries. Does anybody on this list know what I will have to live without if I choose to define inhibit_libc ? Regards, -- Andreas Bach Aaen System Developer, M. Sc. Ericsson Telebit A/S tel: +45 89 38 51 00 Skanderborgvej 232 fax: +45 89 38 51 01 8260 Viby J Denmark e-mail: aba@tbit.dk ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |