After using this flag to re-emerge kde, "-fvisibility=hidden" was added to the CFLAGS in make.conf. This is not good (though it worked quite well with kde).
This could be misread, I'm correct in assuming that make.conf was not modified, but only the CFLAGS for anything that inherits from kde eclass, in which case this is a KDE bug. If I'm wrong, it is still probably a kde bug :P
(In reply to comment #1) > This could be misread, I'm correct in assuming that make.conf was not modified, > but only the CFLAGS for anything that inherits from kde eclass, in which case > this is a KDE bug. > > If I'm wrong, it is still probably a kde bug :P > No. make.conf was changed, so anything would have been compiled with -fvisibilty=hidden. And how is a use flag not a portage issue?
Flameeyes - eh?
(In reply to comment #2) > No. make.conf was changed, so anything would have been compiled with > -fvisibilty=hidden. And how is a use flag not a portage issue? Huh? Well, there's nothing in kde.eclass that would touch make.conf, this is completely bogus. If you are instead asking how the flag works, read http://farragut.flameeyes.is-a-geek.org/articles/2006/05/25/small-and-big-updates There's no other way to enable -fvisibility for KDE stuff. Closing, not a bug.
(In reply to comment #4) > (In reply to comment #2) > > No. make.conf was changed, so anything would have been compiled with > > -fvisibilty=hidden. And how is a use flag not a portage issue? > > Huh? Well, there's nothing in kde.eclass that would touch make.conf, this is > completely bogus. > > If you are instead asking how the flag works, read > http://farragut.flameeyes.is-a-geek.org/articles/2006/05/25/small-and-big-updates > > There's no other way to enable -fvisibility for KDE stuff. > > Closing, not a bug. > Let me be as clear as possible: 1. set kdehiddenvisibility 2. emerge -N world 3. emerge finished, CFLAGS contained -fvisibility=hidden, where before it did not. make.conf had been changed. I don't know how. I've tried to figure it out, and I realize that the kde.eclass doesn't alter make.conf. Admittedly, there are other possibilities: a. I did it and forgot about it. That would be no. I know that it breaks many a thing, and besides, I figured the use flag would handle it for me, that being the point of the use flag. b. Someone else did it. Well, no one else in the house would even know what -fvisibility=hidden means, much less know how to set it in make.conf. That leaves someone breaking in, either through the net, or doing some acutal breaking and entering while I wasn't in the room, and editing the file. Well, it's possible, but as a theory, it doesn't have much else to recommend it. c. Something else did it and it just happened to, well, happen, right before or after setting kdehiddenvisibility. Given that kdehiddenvisibility is related to the option -fvisibility=hidden, that said option was *not* in my CFLAGS when I edited make.conf to set the new use flag, and that it was in my CFLAGS after setting it and re-emerging my kde packages, it seemed reasonable to assume some sort of causal connection. I never claimed it made sense. And yes, obviously, for kdehiddenvisibility to work, it needs to pass the hidden option to the compiler. I understand that. What I don't understand is how and why that option suddenly appeared in my global CFLAGS. That said, I won't alter the bug status, since it'd probably just be set back to what it is now anyway.
> 3. emerge finished, CFLAGS contained -fvisibility=hidden, where before it did > not. make.conf had been changed. I don't know how. I've tried to figure it out, > and I realize that the kde.eclass doesn't alter make.conf. Nor any of the ebuild FWIW, and actually, it does not even alter CFLAGS variable. > Given that kdehiddenvisibility is related to the option -fvisibility=hidden, > that said option was *not* in my CFLAGS when I edited make.conf to set the new > use flag, and that it was in my CFLAGS after setting it and re-emerging my kde > packages, it seemed reasonable to assume some sort of causal connection. I > never claimed it made sense. Okay just to make this clearer. KDE eclass does _not_ inject -fvisibility=hidden option in the CFLAGS variable at all, rather it filters it out. kdehiddenvisibility useflag enables a switch at ./configure that allows to *check* for the availability of -fvisibility=hidden, so the whole stuff is not even touched by portage. You can use grep -r --include 'C*FLAGS' fvisibility=hidden /var/db/pkg to see if you ever had the flag enabled, KDE packages should result without the flag entirely.
OK, my point was not that somehow you were wrong, but that something altered make.conf and it was reasonable, at the time I noticed it, to assume it had something to do with kdehiddenvisibility. That's why I said I would just leave the bug status as is: because it *is* invalid as far as kdehiddenvisibility is concerned. Unfortunately, this means I don't even have an incorrect explanation for why the file was changed.
