* objcopy endian question
@ 1998-05-27 11:14 Joel Sherrill
0 siblings, 0 replies; only message in thread
From: Joel Sherrill @ 1998-05-27 11:14 UTC (permalink / raw)
I have a problem and don't know where to begin looking. Here is the
+ binutils 2.9.1
+ RTEMS targetting a i386 PC
+ host system: RedHat Linux 5.0 x86
+ toolset targets: i386-rtems and i386-rtemself
We are using the grub bootloader to load our linked applications. This
loader expects a.out files. The CPU is already in protected mode when our
application gets control, so we do not have any 16-bit/real mode code. The
build procedure links a "native format" executable (coff for i386-rtems,
elf for i386-rtemself). Then we use objcopy to generate the a.out
expected by the boot loader.
This works marvelously when using the COFF i386-rtems toolset.
When using the ELF based i386-rtemself, it looks like the initialized data
in the a.out file generated by objcopy is endian swapped.
Any suggestions on what might be going wrong? My guess is that something
is not properly honoring endianness.
Thanks in advance for any ideas.
Joel Sherrill Director of Research & Development
joel@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (205) 722-9985
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~1998-05-27 11:14 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1998-05-27 11:14 objcopy endian question Joel Sherrill
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).