All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sam" <iskoo@ms45.hinet.net>
To: <linux-mips@oss.sgi.com>
Subject: # CrossCompiler (Big Endian)
Date: Thu, 13 Jun 2002 17:50:02 +0800	[thread overview]
Message-ID: <01b701c212bf$b1394850$780411ac@sam> (raw)

[-- Attachment #1: Type: text/plain, Size: 357 bytes --]

Hi everybody,

    I got some information to build Little Endian CrossCompiler for mips
    even precompiled binary files, and work well.....

    However, I have to build a Big Endian's one
    Should I get the binutil and glibc for big endian firstly?

    Is there any homepage for reference on web?
    any sample?

    thanks all!

--Sam

[-- Attachment #2: Type: text/html, Size: 1096 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: "Sam" <iskoo@ms45.hinet.net>
To: linux-mips@oss.sgi.com
Subject: # CrossCompiler (Big Endian)
Date: Thu, 13 Jun 2002 17:50:02 +0800	[thread overview]
Message-ID: <01b701c212bf$b1394850$780411ac@sam> (raw)
Message-ID: <20020613095002.zRjefcO5RFZF6YYlu_vmcpgrn85T6jcOf_Cb0BSJo10@z> (raw)

[-- Attachment #1: Type: text/plain, Size: 357 bytes --]

Hi everybody,

    I got some information to build Little Endian CrossCompiler for mips
    even precompiled binary files, and work well.....

    However, I have to build a Big Endian's one
    Should I get the binutil and glibc for big endian firstly?

    Is there any homepage for reference on web?
    any sample?

    thanks all!

--Sam

[-- Attachment #2: Type: text/html, Size: 1096 bytes --]

             reply	other threads:[~2002-06-15  0:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-13  9:50 Sam [this message]
2002-06-13  9:50 ` # CrossCompiler (Big Endian) Sam
  -- strict thread matches above, loose matches on Subject: below --
2002-06-14  7:28 Sam+
2002-06-14  7:28 ` Sam+

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='01b701c212bf$b1394850$780411ac@sam' \
    --to=iskoo@ms45.hinet.net \
    --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 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.