From: "H . J . Lu" <hjl@lucon.org>
To: Andre.Messerschmidt@infineon.com
Cc: linux-mips@oss.sgi.com
Subject: Re: Cross Compiler again
Date: Thu, 22 Nov 2001 10:17:51 -0800 [thread overview]
Message-ID: <20011122101751.A1682@lucon.org> (raw)
In-Reply-To: <86048F07C015D311864100902760F1DD01B5E3CE@dlfw003a.dus.infineon.com>; from Andre.Messerschmidt@infineon.com on Thu, Nov 22, 2001 at 01:42:32PM +0100
On Thu, Nov 22, 2001 at 01:42:32PM +0100, Andre.Messerschmidt@infineon.com wrote:
>
> > May I ask why you want dwarf? FWIW, gcc 2.96 in my RedHat 7.1 mips port
> > supports dwarf, but not as default. I don't know how well it works with
> > dwarf. Yes, both cross compiler running on RedHat/x86 7.1/7.2 and
> > native compiler are provided in my mips port.
> >
> I need dwarf support because my debugger only supports dwarf. (It is an
> integrated simulation environment, where I cannot change the debugger to
> gdb).
>
> Do you have a download link for your mips port?
>
> regards
> Andre
My mini-port of RedHat 7.1 is at
ftp://oss.sgi.com/pub/linux/mips/redhat/7.1/
you should be able to put a small RedHat 7.1 on the mips/mipsel box and
compile the rest of RedHat 7.1 yourselves.
Here are something you should know:
1. The cross compiler hosted on RedHat 7.1/ia32 is provided as a
toolchain rpm. The binary rpms for the mips and mipsel cross compilers
are included. You may need glibc 2.2.3-11 or above to use those
rpms. The glibc x86 binary rpms under RPMS/i386 should be ok.
2. You have to find a way to put those rpms on your machine. I use
network boot and NFS root to do it.
3. install.tar.bz2 has some scripts to prepare NFS root and install
RedHat 7.1 on a hard drive.
4. baseline.tar.bz2 contains the cross build tree.
5. Since everything is cross compiled from x86, which is little endian,
many data files for mips, which is big endian, are either missing or
wrong. To get those data files for mips, you have to rebuild/install
the folowing rpms:
cracklib
glibc
natively on Linux/mips.
Thanks.
H.J.
next prev parent reply other threads:[~2001-11-22 19:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 12:42 Cross Compiler again Andre.Messerschmidt
2001-11-22 18:17 ` H . J . Lu [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-26 16:27 AW: " Andre.Messerschmidt
2001-11-26 20:31 ` Daniel Jacobowitz
2001-11-26 13:38 AW: " Andre.Messerschmidt
2001-11-26 13:48 ` Ralf Baechle
2001-11-26 8:59 Andre.Messerschmidt
2001-11-26 11:22 ` Ralf Baechle
2001-11-22 17:13 AW: " Andre.Messerschmidt
2001-11-25 17:13 ` Daniel Jacobowitz
2001-11-26 11:28 ` Ralf Baechle
2001-11-26 12:06 ` Maciej W. Rozycki
2001-11-22 9:08 Andre.Messerschmidt
2001-11-22 10:03 ` H . J . Lu
2001-11-22 15:53 ` Bradley D. LaRonde
2001-11-22 15:53 ` Bradley D. LaRonde
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=20011122101751.A1682@lucon.org \
--to=hjl@lucon.org \
--cc=Andre.Messerschmidt@infineon.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