------- Comment #7 from rob1weld at aol dot com 2009-01-13 14:38 ------- Let me clarify the accuracy of my meaning:
When I said: "Down in family is not cross compiling." I meant for the purposes of being able to execute 'target' code on the 'host', 'build' or 'target' platform (as when executables that create source code are ran during the build). Technically speaking, _ANY_ difference in 'host', 'build' or 'target' processor, even a _small_ revision, makes it a "cross compile"; we care most (during the build) if we can execute our utilities. --- That reminds me. It would be great if there were a ./configure option to specify a script that would "enable" the other hardware. It could 'wake-up' real hardware and ask it to download / execute / upload results of some code. It could run WINE or QEmu and execute the utility on the target to allow easier cross-porting. A set of 'gnokii-like' scripts could create a simple framework to allow gdb to remotely execute code (port gcc to your cellphone's Operating System). I run gcc to cross compile for my router (Linux 2.6) and cellphone (Symbian). Rob Rob -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38804
