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] |
David Dudley wrote: > > Hey guys! > > I need to build a sparc-rtems-elf cross compiler, hosted on a > i586-pc-linux-elf host. > > I configured the compiler with <configure --host=i586-pc-linux-elf > --target=sparc-rtems-elf --with-newlib> > > When I build the compiler with 'make cross', things go fine, till the end of > stage1. As soon as it tries to do 'stage2', the configure fails, with the > fact that 'xcc can't build executables'. Some stupid questions... What puts you thinking that producing executables for the 'sparc-rtems-elf' should be possible without any more options to define the target? While the 'i586-pc-linux-elf' is a fully defined target, is the 'sparc-rtems-elf' too? In your case I would experiment a little (I not knowing so much about RTEMS), whether it has a standard API with 'syscalls'-like interface to the hardware like Linux. Or does it need a 'glue library' for the target board like an no-opsys embedded 'sparc-elf' would do... What do you mean with these 'stage1' and 'stage2'? AFAIK they belong to the build of a native-GCC, a cross-GCC build has only the 'stage1', unless one calls the building/updating of the native-GCC to just the same version as the 'stage1' (never seen as necessary, I still use egcs-1.1.2 to build gcc-3.0.x). > What's it trying to do, generating the stage2 compiler trying to use the > target compiler, instead of the host? This error normally comes when configuring the target libraries, libiberty and libobjc. When the '--with-newlib' should enable libiberty without any C-library checking, my guess is libobjc... Do you really need libobjc being built just now before your base C-libraries are still unbuilt? So I will agree with David Thompson and suggest you to just install your GCC, and toy with those "Hello World" apps after building and installing your C- library. Later you can consider building the libiberty, libstdc++ and libobjc. Perhaps the Java and Fortran-77 languages with their libs too... The 'project' you stated in your clause after the "Hello guys" is ready now, so be happy and enjoy... Cheers, Kai ------ 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] |