From: Clemens Koller <clemens.koller@anagramm•de>
To: James E Wilson <wilson@specifixinc•com>
Cc: gcc@gcc•gnu.org, linuxppc-embedded@ozlabs•org
Subject: Re: gcc-3.3.3 ppc e500 - Abort of uic from Qt (solved)
Date: Wed, 30 Mar 2005 14:57:33 +0200 [thread overview]
Message-ID: <424AA23D.3090207@anagramm.de> (raw)
In-Reply-To: <424A1936.9020309@specifixinc.com>
Just FYI x-posted to linuxppc-embedded
Hello, James!
Thank you for your hints...
In the meanwhile as I experienced some other strange issues with my
gcc-3.3.3 toolchain, I concentrated to upgrade to the latest
mainstream gcc-3.4.3. It also failed during bootstrapping in
the beginning, but after a 'two-iteration' bootstrap I was able
to move up to 3.4.3:
Here is my buildlog:
./gcc-3.4.3/configure
--enable-languages=c
--enable-shared
--enable-threads=posix
--enable-__cxa_atexit
--enable-nls=yes
--enable-clocale=gnu
make bootstrap
failed with an occasional segfault but let's give it a second chance
make bootstrap
which finished successful!
make install
Ok, now I have a working gcc-3.4.3 at least - well, for c only!
but let me now try a
make distclean
../gcc-3.4.3/configure
--enable-languages=c,c++,objc
--enable-shared
--enable-threads=posix
--enable-__cxa_atexit
--enable-nls=yes
--enable-clocale=gnu
make bootstrap
and voila! successful!
make check
make install
Okay, now, I am back to installing Qt... which also works fine.
uic doesn't crash anymore.
I am pretty sure that my initial toolchain (ELDK3.1 for ppc_8xx)
was somehow broken.
The next step is to get optimized code for the mpc8540 but that's low
priority now.
Best greets,
--
Clemens Koller
_______________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Str. 45/1
81379 Muenchen
Germany
http://www.anagramm.de
Phone: +49-89-741518-50
Fax: +49-89-741518-19
>> /[..]/qt-x11-free-3.3.4/bin/uic -L /[..]/qt-x11-free-3.3.4/plugins
>> -embed designercore [lots of images/*.png's]
>> -o qmake_image_collection.cpp
>> make: *** [qmake_image_collection.cpp] Aborted
>> make: *** Deleting file `qmake_image_collection.cpp'
>
>
> uic is dumping core. We can't really do anything about that, as that
> isn't part of gcc. We need a testcase that we can use to reproduce the
> problem, or evidence of an actual gcc problem.
>
> If this is a gcc miscompilation problem, and you are compiling with a
> high optimization level like -O2, you could try using -O or -O0 instead.
>
> You could try using a different gcc version. Maybe gcc-3.3.4 has a bug
> that isn't present in other earlier or later gcc-3.3.x versions.
>
> You could try debugging uic to figure out why it is failing.
>
> >BTW: What are the most current versions for a toolchain which
> generates >working and efficient code for the MPC8540 (ppc32, e500, spe)?
>
> There are people supporting the e500 target, so it should be working
> reasonably well in any gcc release.
>
> There is a special branch maintained for the e500 by Red Hat, which is
> called gcc-3_4-e500-branch. This can be checked out from our cvs
> repository. I don't know details about this branch other than what is
> on the web site.
> http://gcc.gnu.org/cvs.html#devbranches
> and scroll down to the Architecture-specific section.
parent reply other threads:[~2005-03-30 12:53 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <424A1936.9020309@specifixinc.com>]
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=424AA23D.3090207@anagramm.de \
--to=clemens.koller@anagramm$(echo .)de \
--cc=gcc@gcc$(echo .)gnu.org \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=wilson@specifixinc$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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