From: Yu-Hsueh Chou <chouy@eceserv0.ece.wisc.edu>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] ARM PID big-endian in RedHat 7.1 Question....
Date: Fri, 06 Jul 2001 16:30:00 -0000 [thread overview]
Message-ID: <Pine.SOL.3.96.1010706182832.16938A-100000@eceserv0.ece.wisc.edu> (raw)
Hello all,
I would like to use ARM by big-endian library. I have tried the
binutils-2.10.1,gcc-core-2.95.2, gcc-core-2.95.2, Insight-5.0,
follow all of processes from the ecos web. it works well for
ARM big-endian as it support big-endian library in
/tools/gcc-core-/H-i686-pc-linux-gnu/include/lib/be/libgcc.a
I believe this folder is created by the patch file the ecos web
provided. so that we can use the ARM PID big-endian functions.
Right now, I need to use binutils_2.11.2, gcc-core_3.0,
gcc-g++_3.0. and insight_5.0 from the ARM PID.
but I have no patch file for this new version gcc. how can
I get the big-endian library for ARM by modifying the makefile
of gcc? or anyone can do me a favor to give me advices
to overcome this trouble.
thanks for your any help..
YHChou@viatech.com
next reply other threads:[~2001-07-06 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-06 16:30 Yu-Hsueh Chou [this message]
2001-07-08 12:19 ` Jonathan Larmour
2001-07-06 17:19 Tom Dell
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=Pine.SOL.3.96.1010706182832.16938A-100000@eceserv0.ece.wisc.edu \
--to=chouy@eceserv0.ece.wisc.edu \
--cc=ecos-discuss@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).