public inbox for
 help / color / mirror / Atom feed
From: Joel Sherrill <>
Subject: objcopy endian question
Date: Wed, 27 May 1998 11:14:00 -0000	[thread overview]
Message-ID: <> (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                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (205) 722-9985

                 reply	other threads:[~1998-05-27 11:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).