10.1.2011 16:01, alsp kirjoitti:
checking for sparc-elf-gcc... /d/Development/gcc/gcc_4_3_0_release_o bj/./gcc/xgcc -B/d/Development/gcc/gcc_4_3_0_release_obj/./gcc/ -B/s parc-gcc/sparc-elf/bin/ -B/sparc-gcc/sparc-elf/lib/ -isystem /sparc-gcc/sparc-el f/include -isystem /sparc-gcc/sparc-elf/sys-include checking for suffix of object files... configure: error: cannot compute suffix o f object files: cannot compile I'm also working through a slightly different process for compiling gcc and noticed that it is compiling binutils with the sparc-elf target. This is not something that I was doing and may or not be an influencing factor (mine was compiled for mingw32)?
Is this kind of "clean room" approach really necessary? The alternative would be to download some existing 'sparc-elf' targeted toolchain for MinGW host from the net, then look what it includes and so learn what on earth to build, the toolchain docs probably telling also how to reinvent the wheel via doing the same build oneself... For instance : http://www.gaisler.com/cms/index.php?option=com_content&task=view&id=147&Itemid=31
