Subject: [port-arm32] Building Qt and KDE on 1.3 alpha
To: None <port-arm32@NetBSD.ORG>
From: None <msabin@cromwellmedia.co.uk>
List: port-arm32
Date: 12/18/1997 11:01:40
Just wondering if anyone has managed to diagnose the problems
with building shared versions of the Qt and KDE libraries on
1.3 alpha yet? I've had more or less the same problems as others
have reported in earlier threads on this list (C++ woes), namely
the Qt examples core dumping before __main() is entered. I assume
that something nasty is happening either at the dynamic link step,
or later, when the constructors of global static objects are
called. This happens both with the c++rt0.o and libstdc++.so
from the CD comp set and with the fixes from the FTP site.

Interestingly the compiled version of Qt and and parts of KDE
that Neil has made available seem to work reasonably well.
Unfortunately it isn't possible to build the rest of the KDE
distribution on top of them, because Neil's tools generate
shared binaries with symbols with '.'s in whereas the 1.3 alpha
tools generate executables which expect symbols with '$'s in the
corresponding places. Consequently the rest of the KDE distrib
fails with lots of undefined symbols at link time. This even seems
to affect parts of the KDE build that Neil has released, tho' in
the opposite direction: kdehelp reports something like,

	Undefined symbol __vt.3ios

when run because the corresponding symbol in libstdc++.so (both 
versions) is '__vt$3ios'.

Neil, are there any differences between the toolset you're using
and the one that's on the 1.3 alpha CD?

If anyone has any idea how to fix the problems they'd be much
appreciated. I want to get all of KDE up and running over xmas if
I possibly can. At the moment I'm contemplating a really nasty
hack: replacing all the '.'s in the symbols in Neil's shared libs
with '$'s and rebuilding all the executables. For obvious reasons
I'd really rather not have to do that.

PS if replying by priv mail, please could you cc: to, 

	miles@mistral.co.uk

Cheers,


Miles