FYI, it's not just egcs that's causing the problems when compiling Qt2.2, it's also binutils. According to TrollTech, you need a binutils version that's EXTREMELY old just to be able to properly link Qt2.2 on Alpha. I've posted a bug report on the binutils list, but I've received no replies as of yet. Apparently, there are some function and/or variable definitions which are being merged by either gcc or the linker (most likely the linker) when linking Qt2.2 as a shared library, which causes any binaries linked to the library to segfault on exit (see the gcc docs for the option '-fconserve-space' for reference of the problem). I haven't had time to diagnose the problems further myself yet, though, and I'm not about to upload an ancient binutils since it would effectively kill support for some of the newer ports (ARM, sparc64, etc).
In short, this is a problem that should be fixed upstream in the toolchain. The ICEs that you encounter while compiling Qt2.2 can be worked around by editing the configs/linux-g++-* files and removing the "-O2" optimisation. The library will still fail to link properly (despite giving no warning of such), though. C On Tue, 10 Oct 2000, Matthias Klose wrote: > This won't happen. However feedback about alpha specific bugs in > 2.95.2, which are not in current CVS snapshots, would be welcome. > > Henry House writes: > > Package: g++ > > Version: 1:2.95.2-15 > > > > Please consider adding packages of egcs as an alternative to gcc/g++. It > > would make life easier on the Alpha platform, which has a buggy gcc that > > cannot compile Qt2.2 (it dies with an internal compiler error). This > > is a known gcc/g++ bug on Alphas according to Troll Tech. This bug is > > apparently not found in egcs-2.91.66, which compiles Qt2.2 fine (tested > > on a RedHat/Alpha machine).
