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 02:03:34 -0800 [thread overview]
Message-ID: <20011122020334.A3320@lucon.org> (raw)
In-Reply-To: <86048F07C015D311864100902760F1DD01B5E3CA@dlfw003a.dus.infineon.com>; from Andre.Messerschmidt@infineon.com on Thu, Nov 22, 2001 at 10:08:44AM +0100
On Thu, Nov 22, 2001 at 10:08:44AM +0100, Andre.Messerschmidt@infineon.com wrote:
> Hi.
>
> For my environment I need a compiler that supports dwarf debug information.
> Sadly my precompiled version does not have this support so I tried it on my
> own, using Bradley D. LaRonde's HowTo.
> All went well but I had to learn that GCC 3.0.1 is not able to compile a
> current kernel. So I tried version 2.95.3, but I ran into the same problem
> that I had last time I tried such a thing. When compiling glibc the process
> failed because of a missing -D__PIC__ option. I was told that this has to do
> with a non-MIPS compiler that is used, but the compiler used is my previous
> build static version of gcc.
> I don't know what else may be wrong or where to look. Can anybody enlighten
> me?
>
> Or has anybody a precompiled gcc with dwarf support for download (That is
> able to compile a current kernel, of course. ;-) )?
>
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.
H.J.
next prev parent reply other threads:[~2001-11-22 11:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 9:08 Cross Compiler again Andre.Messerschmidt
2001-11-22 10:03 ` H . J . Lu [this message]
2001-11-22 15:53 ` Bradley D. LaRonde
2001-11-22 15:53 ` Bradley D. LaRonde
-- strict thread matches above, loose matches on Subject: below --
2001-11-22 12:42 Andre.Messerschmidt
2001-11-22 18:17 ` H . J . Lu
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-26 8:59 Andre.Messerschmidt
2001-11-26 11:22 ` Ralf Baechle
2001-11-26 13:38 AW: " Andre.Messerschmidt
2001-11-26 13:48 ` Ralf Baechle
2001-11-26 16:27 AW: " Andre.Messerschmidt
2001-11-26 20:31 ` Daniel Jacobowitz
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=20011122020334.A3320@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