3_3_0_BETA_! Build problems [RESOLVED]

[Segedunum]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 14 Jul 2004 08:41:13, Stephan Binner wrote:
> This is plain wrong: I and others have compiled the release tarballs
> success- fully. The tarballs are recreated for every release (including
> Alpha and Beta releases) until they compile with --enable-final [for the
> testers of course].

So the tarballs did build then? I thought my success was just a freak 
accident. You might want to mention on the 3.3 info page that it is a 
combination of things you can't yet determine. It just tells people that 
kwinrules doesn't compile.

> I have not examined why some people have this problem with kwin (maybe the
> gcc version has an influence or whether you use qt-copy with patches?).
> There were only few reports about this (~3?) and surprisingly no Konstruct
> user AFAIK.   

That's the common theme I would look for. The GCC version, but most 
importantly I think, what version or build of Qt they are using. I have 
always used qt-copy, just to stay up to date, but a combination of GCC, KDE, 
build tools and Qt version may throw problems. I don't really see it as a 
major failure, as this sort of 'combination of circumstances' thing happens 
in every system - commercial, enterprize, expensive or free.

> I see this as a MAJOR quality failure.  No testing at all before it was
> released. 

This is the sort of 'major quality failure', as you put it, you will find in 
business and enterprize systems the world over. What's worse is that many 
software companies will not even return your call to fix it unless you reach 
for the cheque book, and this happens consistently in released software. 
Welcome to the world.

I have built KDE CVS several times over the past few weeks, with DISTCC over a 
wireless network, and with GCC optimizations for my architecture - and not 
once has the core stuff (arts, libs, base) failed to build for any reason. 
Bear in mind that I am no expert in GCC or build internals, or any 
troubleshooting that would need to be done if things went really pear shaped.

Cheers,

David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA9ZwO53OaWc7M8G0RAr+VAJ9OX7jv+JuqI5Z9P6/YdMVXY4a1AwCgn334
9nNxuHug16NX4Kaf+uy1buQ=
=2iyZ
-----END PGP SIGNATURE-----