Summary: | sys-process/psmisc-22.21-r2 fails to emerge in bootstrap | ||
---|---|---|---|
Product: | Gentoo/Alt | Reporter: | Jeffrey Ratcliffe <Jeffrey.Ratcliffe> |
Component: | Prefix Support | Assignee: | Gentoo Prefix <prefix> |
Status: | RESOLVED OBSOLETE | ||
Severity: | blocker | CC: | ericvw |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log |
Description
Jeffrey Ratcliffe
2016-02-02 10:48:24 UTC
Created attachment 424456 [details]
build.log
It is pulling in headers from the host: In file included from /usr/include/curses.h:127:0, from pstree.c:36: /home/jeff/gentoo/usr/include/ncurses/unctrl.h:60:63: error: unknown type name 'SCREEN' NCURSES_EXPORT(NCURSES_CONST char *) NCURSES_SP_NAME(unctrl) (SCREEN*, chtype); Once I patched the source to explicitly take curses.h from the prefix, it emerged with no error. sys-process/procps-3.3.11-r3 fails to emerge with the same error does $(use_with ncurses ncurses=${EPREFIX}/usr) \ work too? I doubt so, but perhaps there's autoconf magic allowing it (In reply to Fabian Groffen from comment #5) > does > $(use_with ncurses ncurses=${EPREFIX}/usr) \ > work too? > > I doubt so, but perhaps there's autoconf magic allowing it The configure.ac script doesn't have a --with-ncurses option at all. It appears that part of the problem may be that ncurses installed the curses.h header into ${EPREFIX}/usr/include/ncurses instead of ${EPREFIX}/usr/include, as it is on my non-prefix system, which means that the --enable-overwrite in the ebuild might not be enough any more. Eric reproduced the bug, and just added himself to the Cc: list. Eric, you might try this workaround: LDFLAGS="${EPREFIX}/usr/include/ncurses" ./bootstrap-prefix.sh (no need to clean your $EPREFIX, bootstrap will resume automatically at last error) (In reply to Daa Jaa from comment #7) > Eric reproduced the bug, and just added himself to the Cc: list. > > Eric, you might try this workaround: > > LDFLAGS="${EPREFIX}/usr/include/ncurses" ./bootstrap-prefix.sh > > (no need to clean your $EPREFIX, bootstrap will resume automatically at last > error) Unfortunately I cleaned my $EPREFIX before I saw this :(. It turns out I am now hitting bug 567300 before I get to emerging sys-process/psmisc. However, if I try stage3 again manually, I eventually get to emerging sys-process/psmisc. Using the workaround as you suggested did not work. I changed the environment variable to be CFLAGS and CPPFLAGS with a leading "-I", which got me further along, but I am still up against bug 567300. Eric, sorry for the loss; I didn't know that a changed LDFLAGS did clean $EPREFIX. Because you are in the emerge -e phase, you might now try this: ./bootstrap-prefix.sh $EPREFIX startscript This should not clean anything, and this may create $EPREFIX/startprefix, which you can execute to use your functionnal $EPREFIX (but not totally up to date). If that fails, try SHELL=bash PATH=$EPREFIX/usr/bin:$EPREFIX/bin ./bootstrap-prefix.sh $EPREFIX startscript This needs revisiting using latest versions and setup. |