On Tue, Aug 12, 2008 at 09:18:55PM -0700, [EMAIL PROTECTED] wrote:
What matters isn't C or assembly, but what runtime is being linked in.
Sounds like what you are saying is that it is useless to get GDB/Armulator and
GCC cross compiler from *different* sources since they are so dependent on each
other. I'm not sure if there is a respected source for GDB/Armulator and GCC
cross compiler tools from same source.
Actually, not at all. It's not about the compiler, it's the runtime.
You can't write even a trivial C program without linking in a C
runtime with it. Your cross compiler environment will be built to run
on something, Linux being the most common, but it might also be
intended for a microkernel or something. The GDB/Armulator isn't
emulating Linux, but a very tiny standalone board. You would need to
link with a runtime appropriate for the environment.
I suggest that you use objdump, especially with '-s' and possibly
'--source' to figure out what code you're generating.
You could study the source code the the GDB armulator to figure out
what it is emulating and try to find a runtime appropriate for that,
or just see if you can get qemu working.
David
--
KPLUG-List@kernel-panic.org
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
