All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yap Tan Sing <tansing@singtel.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Endian problems when migrating program from HP-UX to RedHat Linux
Date: Wed, 18 Apr 2001 03:54:50 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005417@msgid-missing> (raw)

Hi,

Currently I am trying to migrate a program from HP-UX to RedHat 6.2 Linux
(on Dell PowerEdge2400 server). I am facing endian conversion problem. From
HP homepage learned that Linux is little endian whereas HP-UX is big endian.
If I am not wrong there is a gcc option to generate big endian code
(-mbig-endian), but I learned that this option is only applicable to Linux
on advanced RISC machines (ARM). I think Dell PowerEdge2400 server is using
Pentium III so I guess it is not an ARM machine. Do you have any idea how
can I actually get big endian code using my current Dell PowerEdge2400
server? Please help. Thanks in advance.

Thanks & Best Regards,
Yap Tan Sing



             reply	other threads:[~2001-04-18  3:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-18  3:54 Yap Tan Sing [this message]
2001-04-18 19:03 ` [Linux-ia64] Endian problems when migrating program from HP-UX to RedHat Linux Jim Wilson

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=marc-linux-ia64-105590693005417@msgid-missing \
    --to=tansing@singtel.com \
    --cc=linux-ia64@vger.kernel.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.