public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Marcus D. Hanwell" <cryos@gentoo.org>
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	[thread overview]
Message-ID: <200505251748.27667.cryos@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1487 bytes --]

Dear All,

I have just committed a fix to kde.eclass and kde-meta.eclass that disables 
visibility support in KDE 3.4 (thanks to FlameEyes for the patches). This was 
a new feature in KDE 3.4 which has caused at least one obvious bug, and 
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 
3.4 and GCC 4.0 have visibility support. I have been working on a mixed 
system (some of KDE compiled with, and some without visibility support) and 
not encountered any issues.

An easy way to see if you are affected by this bug is to open kasteroids and 
press any key to start a game. If it segfaults then you are affected by this 
bug, recompiling kde-base/kdelibs and kde-base/kasteroids (or 
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 recompile 
for all the bug fixes/enhancements it has. I would recommend most people just 
let KDE components recompile as updates are committed. Please find me on IRC, 
or post comments to the Gentoo bug[2] if you have problems after using the 
updated eclass.

[1] http://bugs.kde.org/show_bug.cgi?id=101542
[2] http://bugs.gentoo.org/show_bug.cgi?id=86898

P.S. PPC, PPC64 and Sparc developers may also want to post this to 
architecture specific lists too.

Thanks,

Marcus
-- 
Gentoo Linux Developer
Scientific Applications | AMD64 | KDE | net-proxy

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2005-05-25 16:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-25 16:48 Marcus D. Hanwell [this message]
2005-05-25 18:02 ` [gentoo-dev] KDE 3.4 visibility support disabled Jason Wever
2005-05-25 23:37 ` [gentoo-dev] " Duncan
2005-05-25 23:57   ` Diego 'Flameeyes' Pettenò
2005-05-26  4:25   ` [gentoo-dev] Re: [gentoo-amd64] " Dan Armak
2005-05-26  7:30     ` [gentoo-dev] " Duncan
2005-05-26 12:26       ` Caleb Tennis
2005-05-26 16:09         ` Andreas Fredriksson
2005-05-26 11:05   ` [gentoo-dev] " Marcus D. Hanwell
2005-05-26 23:23     ` [gentoo-dev] " Duncan

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=200505251748.27667.cryos@gentoo.org \
    --to=cryos@gentoo.org \
    --cc=gentoo-amd64@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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