This morning "ncurses" failed to emerge during the second `emerge -e system' step. From the console log: /local/scratch/portage/sys-libs/ncurses-5.6-r2/work/ncurses-5.6/ncurses/tinfo/lib_termcap.c: In function 'tgetent': /local/scratch/portage/sys-libs/ncurses-5.6-r2/work/ncurses-5.6/ncurses/tinfo/lib_termcap.c:96: warning: cast discards qualifiers from pointer target type /local/scratch/portage/sys-libs/ncurses-5.6-r2/work/ncurses-5.6/ncurses/tinfo/lib_termcap.c: At top level: /local/scratch/portage/sys-libs/ncurses-5.6-r2/work/ncurses-5.6/ncurses/tinfo/lib_termcap.c:191: error: conflicting types for 'tgetflag' ../include/term.h:781: error: previous declaration of 'tgetflag' was here /local/scratch/portage/sys-libs/ncurses-5.6-r2/work/ncurses-5.6/ncurses/tinfo/lib_termcap.c:219: error: conflicting types for 'tgetnum' ../include/term.h:782: error: previous declaration of 'tgetnum' was here /local/scratch/portage/sys-libs/ncurses-5.6-r2/work/ncurses-5.6/ncurses/tinfo/lib_termcap.c:248: error: conflicting types for 'tgetstr' ../include/term.h:778: error: previous declaration of 'tgetstr' was here make[1]: *** [../obj_s/lib_termcap.o] Error 1 make[1]: *** Waiting for unfinished jobs.... make[1]: Leaving directory `/local/scratch/portage/sys-libs/ncurses-5.6-r2/work/narrowc/ncurses' make: *** [all] Error 2 * ERROR: sys-libs/ncurses-5.6-r2 failed: Just speculating, the same emerge succeded yesterday. Today another version of portage is in charge (yesterday: 2.2.00.11322, today: 2.2.00.11334). Can this have effected things?
Absolutely not. Was the host OS updated?
(In reply to comment #1) > > Was the host OS updated? > No, no changes since yesterday.
(In reply to comment #0) > Just speculating, the same emerge succeded yesterday. Today another version of > portage is in charge (yesterday: 2.2.00.11322, today: 2.2.00.11334). Can this > have effected things? froog from irc reports the same on macos (iirc). bootstrapped portage works, upgraded portage does not. 10:34 <@darksiide> froog: bug 234050 ? 10:34 <+snackb0t> Bug [ 234050 ] Reporter [ rabbe@bahnhof.se ] Desc [ ncurses fails to emerge in prefix portage ] Status [ NEW ] https://bugs.gentoo.org/234050 10:35 < froog> darksiide: indeed, that's the one 10:36 <@darksiide> =/ 10:36 <@darksiide> hmm, what changed with ncurses 10:36 < froog> when I use the bootstrap portage it works, after I install a new portage, I get that error 10:37 <@darksiide> and if you downgrade portage? 10:37 <@darksiide> yea,abs nothing has changed with ncurses 10:37 < froog> I'm currently doing a 'emerge -e system' using the bootstrap portage 10:38 < froog> it works with that version 10:39 < froog> actually, I get another error as well 10:39 < froog> if I update portage 10:39 <@darksiide> oh? 10:40 < froog> and then do an 'emerge -e portage' I get a strange error about id 'portage' not being known, something like that. Can't remember the exact message Is the latter bit related?
the latter is what fabrice reported on gentoo-alt ML
I removed the latest portage version, sicne froog reported that ncurses compiles again with the one before last. @rabbe: please test/report if your nightly build indeed passes again with this change
I just recalled that the latest portage included EAPI 2_pre2, which messes around with src_* functions. That could be a problem. I'm trying to reproduce the problem here now.
I can reproduce. It looks like the first configure being run is not correct, as it doesn't include any of the special configure arguments that the ebuild constructs. Comparing to an older portage the first configure call has the correct flags. Looks like EAPI 2_pre2 could be the cause of this.
Sucessful bootstrapping now, with portage-2.2.00.11322 and ncurses-5.6-r2.
thanks, problem found, portage bug, prefix only.
