I have just installed Gentoo ver1.2 and tried to install vi as my first install. (Nano just doesn't do it for me.) I did the following as root:

cd /usr/portage/app-editors/vi
emerge vi-3.7.ebuild

The build appears to work fine - no error messages. But when I run vi (even without a file parameter), I immediately get:

Segmentation fault

I'm using the same Portage version that I built the system with, which was downloaded only 4-5 days ago. Should I presume that I used the wrong configuration (from "make menuconfig") when I built the system? I'm very willing to do a trial-and-error thing, but it would be cool if I could pare down the possible trials first with a little advice.

I blieve this is a semi common problem. I know i had it when I started w/ gentoo.

I ended up just doing an "emerge vim".. It does emerge a bunch of things that take time (like X), but you're probably going to do that anyways, if you haven't already.

I tried vim and it works fine. Thanks. I was mostly concerned that I had a larger problem (and that it was my problem, not a problem with vi), since this was my first "emerge" after installing Gentoo.

Maybe it still is a problem with my configuration in some way (and yours also?) and I would be interested to know if anybody has been able to emerge and run vi. (And if so, then why did my attempt fail?) But at least if it is a problem, it's not a killer, and I do now have a decent editor. Thanks._________________Brian Matson
(linux newbie)

It's common for an ebuild to fail for you and not me or vise versa, gentoo is sort of like you own private distribution of linux therefore no two systems are identical.

Make sense?

Yes it does make sense, thanks. At least being aware of that puts a new perspective on whether or not I've make a configuration "mistake" or not. And it sure makes me appreciate more the amount of effort that has gone into putting together existing distributions of Linux. Thanks for the insight._________________Brian Matson
(linux newbie)

It may be one package confilicting with another, and not something you yourself did at all.

What I always do if a package won't compile is pull the source out of distfiles and try to compile it myself, if it does then I look closely at the ebuild to figure out the problem, if it still won't compile manually I know it is something else entirely._________________This message self destructed a long time ago.