I emerged vi using the P6 (mach=i686) opts as suggested in the /etc/make.conf file. Every time I try and spawn vi it seg faults. Vi/Vim is a must for any distro!!!
gcc-2.95.3 or gcc-3.1?
I'm having the same problem. I'm running i686 as well, with suggested defaults listed in /etc/make.conf. gcc --version reports 2.95.3
Can you strace the startup.. I cannot recreate the problem on my machine so far. I have the same i686 compile flags.
I also have this problem, i686 suggested defaults in /etc/make.conf too! Just so you know vim still works fine (or at least for me). It was funny one of the first things I tried to install was vi and it gave me an EVIL first impression of gentoo, but everything since then has been perfect=] See ya
same problem with app-editors/vi-3.7 gcc --version 2.95.3 CHOST="i586-pc-linux-gnu" CFLAGS="-march=i586 -O3 -pipe" CXXFLAGS="-march=i586 -O3 -pipe" strace is attached
Created attachment 1668 [details] strace for vi-3.7
forgotten app-editors/vim-6.1-r7 works fine
*** Bug 3682 has been marked as a duplicate of this bug. ***
The problem is the "linux" TERM setting. Setting TERM to "vt220", for example, works just great. vi also works fine in an xterm. AFAICT, it has absolutely nothing to do with build optimizations.
yeah guy you are right. i've done export TERM=vt100 and vi started without segfault
Ok.. What term are you having the most issue's with? aterm seems to give me the most problems.. it works in xterm becuase it has a termcap file.. But get back to me with your terminal type aterm or Eterm whatever .. Please
In fact the issue is when no TERM is selected If you do "export TERM=VT100" by example, before running vi, it works, vi also works in XTerm. This is not really a problem so, but i suggest that a default term be set in the profiles by the install of "vi" ... What do you think about it ?
Probably not a bad idea.. though it seems to be a ncurses issue.. which the newest version seems to fix the problem on some peoples machines, but not mine :-/, so I'm assuming it will be a issue on others as well.. the best thing to do at this point while I work on a solution is not use TERM=linux.. not a very good solution but it works
From what I starting to understand using TERM=linux inside of X is a very bad idea.. it triggers ncurses aware applications to expect a linux TERM which most x based terms do not fully implament for example vcs,vcsa which no X based term can do. Naz
vcs,vcsa or located in /dev.. This is none critical.. and please inform me of any Terms that set TERM to linux.. those need to be modified not to do so
