Can't build sys-libs/ncurses-5.7-r3 Reproducible: Always Steps to Reproduce: 1.try to upgrade ncurses 2.watch it fail 3.not error of -pg being incompatible with -fomit-frame-pointer Actual Results: Gcc tells me I suck Expected Results: success This should have been a blocker of 299159 stabilization request....
Created attachment 216002 [details] build.log
Created attachment 216005 [details] emerge-info
Never ever cc anyone yourself...this just makes the whole wrangling system absurd. From your build.log: i686-pc-linux-gnu-gcc: -pg and -fomit-frame-pointer are incompatible base-system: -fomit-frame-pointer should be filtered or -pg excluded.
Sorry, wrong resolution. *** This bug has been marked as a duplicate of bug 184722 ***
(In reply to comment #3) > Never ever cc anyone yourself...this just makes the whole wrangling system > absurd. > many apologies, it will not happen again. > From your build.log: > i686-pc-linux-gnu-gcc: -pg and -fomit-frame-pointer are incompatible > > base-system: -fomit-frame-pointer should be filtered or -pg excluded. >
(In reply to comment #4) > Sorry, wrong resolution. > > *** This bug has been marked as a duplicate of bug 184722 *** > For those of you reading this bug let me save you reading through a bunch of garbage to find the solution. Remove profile use flag or remove -fomit-frame-pointer cflag. Personally, I'm removing the use flag. Why EVERY OTHER GENTOO PACKAGE builds fine like this and ncurses doesn't is completely unknown to me. But hey, they aren't going to fix it for you so do it yourself. Don't think I ever used profiling, and -fomit-frame-pointer is default cflags for x86 so the choice is clear enough for me.
stupid user configurations result in a build failure. not an ncurses bug.
Okay, I'm sorry to do this because it's 75% chance of me getting shut down and yelled at, BUT.... Instead of giving the users a gcc error and watching more needless bugs get opened for, and I grant, obvious user stupidity... maybe we could educate our users? use profile && has -fomit-frame-pointer ${CFLAGS}; then die "You can't use -fomit-frame-pointer and use=profile. Ever. How are you still breathing with an IQ so low?"; fi Adding a stanza like this to ncurses would not just silently filter out user stupidity, but would actively cause the users to educate themselves. Having gcc bug out about a bad setup, user fault or not, is going to cause more noise on the bug tracker and more user pain. Please seriously consider adding this to sys-libs/ncurses. Even better, you could make all the other ebuilds stop just filtering the flag and educate users there too: media-sound/mpd/mpd-0.15.6.ebuild xfce-base/xfce4-session/xfce4-session-4.6.1-r1.ebuild xfce-base/xfconf/xfconf-4.6.1-r1.ebuild net-analyzer/wireshark/wireshark-1.2.5.ebuild I'm fine with not correcting stupidity, but we should handle this per ebuild or throw it in an eclass. Filtering for user stupidity is bad, and that's the way most ebuilds handle this. Leaving users in the dark with a gcc error and closing tickets with comments which can be summed up with the word "moron" is even less useful. Can we PLEASE do something constructive for this issue?
Apologies, correct syntax for fix is: use profile && has -fomit-frame-pointer ${CFLAGS} && die "You can't use -fomit-frame-pointer and use=profile. Ever. How are you still breathing with an IQ so low?"
it's still a dupe, and those packages shouldnt be filtering. i'll put something in profile.bashrc. *** This bug has been marked as a duplicate of bug 184722 ***