From: "H. J. Lu" <hjl@lucon.org>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Gcc v2.96 versus Trolltech QtEmbedded Window System
Date: Sat, 13 Jul 2002 09:00:16 -0700 [thread overview]
Message-ID: <20020713090016.A18723@lucon.org> (raw)
In-Reply-To: <023e01c22a5e$c013f120$10eca8c0@grendel>; from kevink@mips.com on Sat, Jul 13, 2002 at 01:15:54PM +0200
On Sat, Jul 13, 2002 at 01:15:54PM +0200, Kevin D. Kissell wrote:
> I am trying to build the GPL version of the Trolltech
> QT embedded windowing system on my Malta, using
> what I believe to be H.J. Lu's most recent tool chain:
>
> [root@localhost release-emb-generic]# g++ -v
> Reading specs from /usr/lib/gcc-lib/mipsel-redhat-linux-gnu/2.96/specs
> gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-110.1)
>
> The QT build process is a little unusual - the configure
> script causes a fairly huge (640KB) C++ source file
> to be generated, which is then thrown at the compiler.
> I would expect that to take a while, but after about
> 20 hours with zero output passed to the assembler
> stage (it runs with -pipe) and the gradual accretion
> of about 90MB of virtual memory (on my poor 32MB
> system) I concluded that it was probably trapped in
> an infinite loop. As I have seen this sort of thing occur
> in the past in optimizer stages, I hacked the makefile
> to replace -O2 with -O0. It hasn't run for 20 hours
> at -O0 yet, but after a couple of hours the memory
> allocation dynamic looks to be the same, only faster
> (72MB after only a couple of hours), so I'm not
> optimistic.
>
> My questions to the assembled panel of experts are:
>
> Are there known problems with gcc 2.96.110.1 in
> this regard?
Have you tried the same C++ code with the same version of the cross
toolchain on Linux/x86? It may just take huge amount of memory.
>
> Is there a native toolchain that would be more
> likely to be able to handle the build of QT?
> I'm considering trying the 2.95 set on Maciej's
> site out of desperation.
>
You can try my gcc 3.1 for RedHat 7.3. But it may need more memory.
H.J.
next prev parent reply other threads:[~2002-07-13 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-13 11:15 Gcc v2.96 versus Trolltech QtEmbedded Window System Kevin D. Kissell
2002-07-13 11:15 ` Kevin D. Kissell
2002-07-13 12:15 ` Bradley D. LaRonde
2002-07-13 12:15 ` Bradley D. LaRonde
2002-07-13 16:00 ` H. J. Lu [this message]
2002-07-14 9:53 ` Kevin D. Kissell
2002-07-14 9:53 ` Kevin D. Kissell
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=20020713090016.A18723@lucon.org \
--to=hjl@lucon.org \
--cc=kevink@mips.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