Well, it finally worked. �I just put -ncurses in the USE variable (I didn't have it in to begin with). �The reason I did that was I had filed a bug and misunderstood one of the responses and thought I had to put -ncurses in the USE variable. �Turns out that's not what he meant. �However, the system is past the bootstrap and emerging the system. Who knows???
> I'm building from stage 1 on a PIII dual 933 system (after I figured out > why it was so slow). It works fine but twice in a row I've gotten an > ncurses error that causes it to fail. It's NOT caused by a failure to > env-update/source .... > > The first time I did the build I did the env-update, source /etc/profile > then set up make.conf and then scripts/bootstrap.sh in /usr/portage. > This build failed with the error > > configure: error C++ preprocessor /lib/cpp fails sanity check" > Error sys-libs/ncurses-5.3-r1 failed. > Function econf, line 14, exitcode 1 > econf failed > > So I env-updated, source /etc/profile and did a scripts/bootstrap.sh again. > > Exact same failure. > > Any ideas on what broke here? > > Thanks. -- Brett I. Holcomb AKA Grunt <>< -- [EMAIL PROTECTED] mailing list
