Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Brady Brown <bbrown@ti.com>
To: SGI news group <linux-mips@oss.sgi.com>
Subject: egcs 1.0.3a-2 crosscompiler behavior
Date: Wed, 19 Jul 2000 15:11:37 -0600	[thread overview]
Message-ID: <39761989.D37E89FE@ti.com> (raw)

I have several steps in my build process where I use the linker to link
a pure binary file (usually a zipped image) into a relocatable elf file,
which is then linked with other elf files to create a final image. I am
running the mipsel-linux cross compiler tool chain on an i386. After
upgrading the tools to egcs 1.0.3a-2 the linking of this binary file
fails.

Example:
mipsel-linux-ld -T link.script -r -b binary image.gz -o image.o

link.script file contents are:
OUTPUT_FORMAT("elf32-littlemips")
OUTPUT_ARCH(mips)
SECTIONS
{
    .data :
    {
        image_start = .;
        *(.data)
        image_end = .;
      }
}

The normal output from the old linker was:
mipsel-linux-ld: image.gz: compiled for a little endian system and
target is little endian

The new linker gives:
mipsel-linux-ld: image.gz: compiled for a little endian system and
target is big endian
File in wrong format: failed to merge target specific data of file
image.gz?
make[1]: *** [image.o] Error 1

I have been unable to figure out why the linker thinks the target is big
endian and have yet to find a way to get this to work. Any ideas?
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Brady Brown (bbrown@ti.com)       Work:(801)619-6103
Texas Instruments: Broadband Access Group
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

             reply	other threads:[~2000-07-19 21:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-19 21:11 Brady Brown [this message]
2000-07-19 22:58 ` egcs 1.0.3a-2 crosscompiler behavior Ulf Carlsson

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=39761989.D37E89FE@ti.com \
    --to=bbrown@ti.com \
    --cc=linux-mips@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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