Re: [gentoo-dev] Re: automatically killing invalid CFLAGS/warning about bad CFLAGS
I find it a little annoying, but not that annoying. I have a few checks to make on libsdl, since it did fail with my CFLAGS settings. Perhaps it's not -fvisibility-inlines-hidden. As for KDE apps, didn't someone mention earlier that these ebuilds now filter -fvisibility-inlines-hidden? This doesn't fix the problem with the flag, it just covers it up. In any case, it's a possible problem that I will put up with. btw, I'm not using visibility=hidden (dev-only flag, not for users). --James Potts On 4/27/06, R Hill [EMAIL PROTECTED] wrote: James Potts wrote: -fvisibility-inlines-hidden not only breaks a number of kde apps afaik (it's filtered now), Again, probably -fvisibility=hidden. Many people have had success building KDE with both flags enabled lately, so maybe that's something that could be revisited when 4.1 goes ~arch. Getting off topic here, so see http://forums.gentoo.org/viewtopic-t-426814.html if you're interested. but it also seems to break SDL (using noflagstrip). -fvisibility-inlines-hidden affects C++ code. libsdl is written in C. ;) It's not broken enough that I'm going to remove it from my global CXXFLAGS, tho, especially since if it breaks something I know about it right away (compile error) and can remove the flag for that package. Right, so you don't find that `sleep 5` at the beginning of every single emerge just a little annoying? ;) --de. -- gentoo-dev@gentoo.org mailing list -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Re: automatically killing invalid CFLAGS/warning about bad CFLAGS
James Potts wrote: -fvisibility-inlines-hidden not only breaks a number of kde apps afaik (it's filtered now), Again, probably -fvisibility=hidden. Many people have had success building KDE with both flags enabled lately, so maybe that's something that could be revisited when 4.1 goes ~arch. Getting off topic here, so see http://forums.gentoo.org/viewtopic-t-426814.html if you're interested. but it also seems to break SDL (using noflagstrip). -fvisibility-inlines-hidden affects C++ code. libsdl is written in C. ;) It's not broken enough that I'm going to remove it from my global CXXFLAGS, tho, especially since if it breaks something I know about it right away (compile error) and can remove the flag for that package. Right, so you don't find that `sleep 5` at the beginning of every single emerge just a little annoying? ;) --de. -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Re: automatically killing invalid CFLAGS/warning about bad CFLAGS
Harald van Dijk wrote: On Thu, Apr 13, 2006 at 09:39:28PM -0600, R Hill wrote: Donnie Berkholz wrote: R Hill wrote: There's an endless number of CFLAGS that could be warned about, and just as many situations where they're actually useful. Aside, I've yet to hear of _anything_ that's broken because of -fvisibility-inlines-hidden. (course someone will undoubtedly point one out now ;)) How about kde? Close, that's -fvisibility=hidden. :) http://gcc.gnu.org/gcc-4.0/changes.html#visibility --de. kdevelop used to not compile with -fvisibility-inlines-hidden, not sure if that's changed now. Sure enough it's changed - kde.eclass now filters all this visibility crap (-fvisibility=hidden *and* -fvisibility-inlines-hidden) by default because it bombs out really badly... :) http://groups.google.de/group/linux.gentoo.dev/browse_frm/thread/f43fac917352bb51/5093e84871f08de6?lnk=st More fun: https://bugs.kde.org/show_bug.cgi?id=109386 http://planet.gentoo.org/developers/flameeyes/2005/11/16/happy_the_visibility_stuff_goes_away http://planet.gentoo.org/developers/flameeyes/2005/10/06/ehi_i_m_invisible -- Best regards, Jakub Moc mailto:[EMAIL PROTECTED] GPG signature: http://subkeys.pgp.net:11371/pks/lookup?op=getsearch=0xCEBA3D9E Primary key fingerprint: D2D7 933C 9BA1 C95B 2C95 B30F 8717 D5FD CEBA 3D9E ... still no signature ;) signature.asc Description: OpenPGP digital signature
[gentoo-dev] Re: automatically killing invalid CFLAGS/warning about bad CFLAGS
Patrick McLean posted [EMAIL PROTECTED], excerpted below, on Thu, 13 Apr 2006 15:50:11 -0400: For about a month now, we (amd64) have had some code in our profile.bashrc that filters CFLAGS that are unrecognized by gcc, and warnings the user about bad CFLAGS. So far it has worked fairly well, and it has really cut down on the number of bugs that filed by people with extreme ricer CFLAGS. It might be an idea to have something similar in the global bashrc, and have a system for arches to customize the CFLAGS that are warned about. The code is at gentoo-x86/profiles/default-linux/amd64/profile.bashrc for those who want to see it. Not just ricer flags (or I wouldn't call them that anyway and unlike some, can explain each one and why I use it)... I'm running gcc-4.0.x and 4.1.0, the latter as my default compiler, in addition to 3.4.6. One of the flags I use (-ftree-pre) isn't recognized by 3.4.x, and it has been a bit of a hassle removing it each time I revert to 3.4.6 to test something or other. I've been /very/ impressed with the way this works, as now I don't have to worry about killing the flag when I switch gccs, because the profile code kills it for me! =8^) The first time I noticed it, I wondered what kind of magic the ebuild was doing. Then I saw it on a couple others, and then happened across it while reviewing the profile. It works! =8^) -- 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
[gentoo-dev] Re: automatically killing invalid CFLAGS/warning about bad CFLAGS
Patrick McLean wrote: For about a month now, we (amd64) have had some code in our profile.bashrc that filters CFLAGS that are unrecognized by gcc, and warnings the user about bad CFLAGS. The broken flags part is useful. So far it has worked fairly well, and it has really cut down on the number of bugs that filed by people with extreme ricer CFLAGS. It might be an idea to have something similar in the global bashrc, and have a system for arches to customize the CFLAGS that are warned about. There's an endless number of CFLAGS that could be warned about, and just as many situations where they're actually useful. Aside, I've yet to hear of _anything_ that's broken because of -fvisibility-inlines-hidden. (course someone will undoubtedly point one out now ;)) Maybe if the sleep 5 were removed this would be helpful. Right now i'm just rm-ing the bashrc in my --sync alias. --de. -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Re: automatically killing invalid CFLAGS/warning about bad CFLAGS
R Hill wrote: There's an endless number of CFLAGS that could be warned about, and just as many situations where they're actually useful. Aside, I've yet to hear of _anything_ that's broken because of -fvisibility-inlines-hidden. (course someone will undoubtedly point one out now ;)) How about kde? signature.asc Description: OpenPGP digital signature
[gentoo-dev] Re: automatically killing invalid CFLAGS/warning about bad CFLAGS
Donnie Berkholz wrote: R Hill wrote: There's an endless number of CFLAGS that could be warned about, and just as many situations where they're actually useful. Aside, I've yet to hear of _anything_ that's broken because of -fvisibility-inlines-hidden. (course someone will undoubtedly point one out now ;)) How about kde? Close, that's -fvisibility=hidden. :) http://gcc.gnu.org/gcc-4.0/changes.html#visibility --de. -- gentoo-dev@gentoo.org mailing list
