From: Daniel Jacobowitz <dan@debian.org>
To: atul srivastava <atulsrivastava9@rediffmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: problem with big endian binutils..?
Date: Tue, 12 Nov 2002 11:23:10 -0500 [thread overview]
Message-ID: <20021112162310.GA2934@nevyn.them.org> (raw)
In-Reply-To: <20021112132512.31137.qmail@mailweb34.rediffmail.com>
On Tue, Nov 12, 2002 at 01:25:12PM -0000, atul srivastava wrote:
> Have anybody confirmed stability of binutils for big endian
> mips?
> while little endian gives me no problem
> but i am simply unable to make a working big endian ramdisk.
>
> specific problem is in identifying the e_type and e_machine fields
> in elf header of executables.
> expected value of e_type is 0x2(ET_EXEC) amd e_machine is
> 0x8(EM_MIPS)
> but those are read as 0x200 and 0x800 respectivly ..this is
> obviously the endianness problem.
Binutils is just fine. This is a problem with whatever's reading them.
> I have tried big endian ramdisk from
> ftp://ftp.ltc.com/pub/linux/mips/ramdisk/ramdisk
> and also tried compiling one using uclibc package , both
> failed because of same reason.
>
> when i run file command on those executables after mounting the
> ramdisk on my host i get o/p like
>
> ELF 32-bit LSB executable, MIPS R3000_BE - invalid byte order,
> version 1, statically linked, stripped
>
> though i see lot of mails regarding "invalid byteorder" but I
> didn't find specific suggestions.
It's normal. The 'file' output is outdated.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-11-12 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-12 13:25 problem with big endian binutils..? atul srivastava
2002-11-12 16:23 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-12 13:22 atul srivastava
2002-11-12 17:48 ` Ralf Baechle
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=20021112162310.GA2934@nevyn.them.org \
--to=dan@debian.org \
--cc=atulsrivastava9@rediffmail.com \
--cc=linux-mips@linux-mips.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.