From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j4PGmRga000470; Wed, 25 May 2005 16:48:27 GMT Received: from palladium.cryos.net ([80.68.90.219]) by smtp.gentoo.org with esmtp (Exim 4.43) id 1Daz3a-0002aT-92; Wed, 25 May 2005 16:48:34 +0000 Received: from localhost (localhost [127.0.0.1]) by palladium.cryos.net (Postfix) with ESMTP id 28CEA5C024; Wed, 25 May 2005 18:03:48 +0100 (BST) Received: from palladium.cryos.net ([127.0.0.1]) by localhost (palladium [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 09630-03; Wed, 25 May 2005 18:03:43 +0100 (BST) Received: from linux.cryos.net (linux.cryos.net [217.155.144.218]) (using SSLv3 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by palladium.cryos.net (Postfix) with ESMTP id D99D35C023; Wed, 25 May 2005 18:03:42 +0100 (BST) From: "Marcus D. Hanwell" Organization: Gentoo To: gentoo-dev@lists.gentoo.org, gentoo-amd64@lists.gentoo.org, gentoo-user@lists.gentoo.org Subject: [gentoo-dev] KDE 3.4 visibility support disabled Date: Wed, 25 May 2005 17:48:20 +0100 User-Agent: KMail/1.8 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1494566.2ktUCcSFNu"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200505251748.27667.cryos@gentoo.org> X-Virus-Scanned: by amavisd-new at palladium.cryos.net X-Archives-Salt: a72f8667-b3af-4cba-888d-f62f95c734b3 X-Archives-Hash: a0f1c566bb4b9cb8a957352db37b94d7 --nextPart1494566.2ktUCcSFNu Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Dear All, I have just committed a fix to kde.eclass and kde-meta.eclass that disables= =20 visibility support in KDE 3.4 (thanks to FlameEyes for the patches). This w= as=20 a new feature in KDE 3.4 which has caused at least one obvious bug, and=20 possibly others that are less obvious[1]. Anyone still using GCC 3.3 will not be affected by this bug at all as only = GCC=20 3.4 and GCC 4.0 have visibility support. I have been working on a mixed=20 system (some of KDE compiled with, and some without visibility support) and= =20 not encountered any issues. An easy way to see if you are affected by this bug is to open kasteroids an= d=20 press any key to start a game. If it segfaults then you are affected by thi= s=20 bug, recompiling kde-base/kdelibs and kde-base/kasteroids (or=20 kde-base/kdegames) with the patched eclasses will cure this problem. KDE 3.4.1 will be released soon, and so will prompt most people to recompil= e=20 for all the bug fixes/enhancements it has. I would recommend most people ju= st=20 let KDE components recompile as updates are committed. Please find me on IR= C,=20 or post comments to the Gentoo bug[2] if you have problems after using the= =20 updated eclass. [1] http://bugs.kde.org/show_bug.cgi?id=3D101542 [2] http://bugs.gentoo.org/show_bug.cgi?id=3D86898 P.S. PPC, PPC64 and Sparc developers may also want to post this to=20 architecture specific lists too. Thanks, Marcus =2D-=20 Gentoo Linux Developer Scientific Applications | AMD64 | KDE | net-proxy --nextPart1494566.2ktUCcSFNu Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQBClKxbzgRsaX1BF70RAodQAJ9mAsgHNXFjBVIia+yPzBUGI5XqYgCgn1Wx rA/y3WLB6P71iRTXpXbOhKs= =BKqU -----END PGP SIGNATURE----- --nextPart1494566.2ktUCcSFNu-- -- gentoo-dev@gentoo.org mailing list