From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Cc: gentoo-amd64@lists.gentoo.org, gentoo-user@lists.gentoo.org
Subject: [gentoo-dev] Re: Re: KDE 3.4 visibility support disabled
Date: Thu, 26 May 2005 00:30:07 -0700 [thread overview]
Message-ID: <pan.2005.05.26.07.30.01.751597@cox.net> (raw)
In-Reply-To: 200505260725.29929.danarmak@gentoo.org
Dan Armak posted <200505260725.29929.danarmak@gentoo.org>, excerpted
below, on Thu, 26 May 2005 07:25:21 +0300:
> That's going to kill it everywhere, gcc4 included. The way KDE uses hidden
> visibility is itself broken - not gcc. Until that's fixed, we're disabling
> visibility support in kde. (There was a separate bug in gcc itself which got
> fixed, which may have confused some people...)
Ahh... yes. Distinctive separate bug makes more sense, now. I had only
known about the gcc bug.
So the KDE problem... Is that what's causing all those virtual function
but destructor isn't virtual type warnings whenever I compile a KDE ebuild
with gcc4?
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-05-26 7:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 16:48 [gentoo-dev] KDE 3.4 visibility support disabled Marcus D. Hanwell
2005-05-25 18:02 ` 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 ` Duncan [this message]
2005-05-26 12:26 ` [gentoo-dev] " 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=pan.2005.05.26.07.30.01.751597@cox.net \
--to=1i5t5.duncan@cox.net \
--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