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] |
On Thu, 25 Jan 2001, Andreas Bach Aaen wrote: > > Thanks for the info, but using --with-newlib seems to fail for me: > > 1) first I build and installed binutils > 2) then I tried to build gcc > gcc-build]$ ../gcc-2.95.2/configure > --target=powerpc-eabi > --prefix=/tools/linux-x86 --enable-languages=c --with-newlib > --without-dwarf2 ; make ^^^^ You're not just building the C compiler + libgcc, but also telling make to build everything it can. In your case, make will also try to build libiberty for target, and of course that'll fail. Instead of ``make'', use make LANGUAGES=c all-gcc make LANGUAGES=c install-gcc [ LANGUAGES=c is unnecessary since you've only enabled C, but this is there for others benefit ] Use the installed C compiler to build your target runtime, install it, and *then* return to GCC and make everything. Mumit ------ 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] |