If you attempt an install by chrooting from an already installed distro, "emerge system" stops during the ncurses ebuild. It says: The ebuild did not complete successfully Function src-compile, line16, Exitcode 2 (no error message) emerge avorting on /user/portage/sys- libs/ncurses/ncurse5.5.2.20020511.ebuild (On a related note, I wouldn't be chrooting from another distro if it wasn't for bug 2109.) Thanks!
yes, this is true even from gentoo chroot.. bad ncurses.
Matt, any ideas on this? the version of ncurses leads me to think it is gcc-3 related. ckelsh, is it a gcc-3 profile?
> ckelsh, is it a gcc-3 profile? there is no gcc-3.1 profile for ppc (yet), so I would have to think no
http://bugs.gentoo.org/show_bug.cgi?id=3491 this has some (possibly) helpful info for this issue?
I think I know the cause of this: there is a patch that fixes it, but it's bzipped. bzip was missing as a dep and so the aptch wasn't applied in src_unpack and the ebuild failed compiling. I've now added the bzip2 dep to ncurses (it just rearranges the emerge system order a little), please check if that helps.
It worked for me on a new bootsrap I did 2 days ago, so it must clear up the problem (?)
This was fixed by adding the bzip2 dep to ncurses
Actually it is now fixed, bzcat does not exist at this early stage of a build (if building ala autobuildimg style), modified to use bunzip2 -c instead of bzcat.