VIM 6.1-r7 compile failure

Federkern · n00b Joined: 22 Jun 2002 Posts: 1

Move files from /usr/local/include to /usr/include and delete /usr/local/include . emerge vim should work now.

Federkern

Lovechild · Posted: Sat Jun 22, 2002 4:25 pm Post subject:

That seemed to fix it, funny since I only had /usr/local/include to fix tetex-1.0.7-r9 - so it's all good now..

Lovechild · Posted: Sat Jun 22, 2002 6:09 pm Post subject:

Sadly that wasn't the end of it..

wont-i · n00b Joined: 06 Jun 2002 Posts: 8

I pulled in the extra patches that Bram Moolenaar has posted, and one of them fixed this problem for me. Don't ask me which specific one, because I don't know. :-)

Having said that, the patches in the /usr/portage/app-editors/vim/files directory only go up to 6.1.074, while the ones I grabbed go up through 6.1.100. I got them from http://ftp.at.vim.org/pub/vim/patches/?fisel=all. One thing to note: If you grab the patches from the VIM ftp site, only put the ones above 6.1.074 in the files directory, as there are ones that are specific to non-unix platforms that will cause patch to pause and ask for "file to patch" confirmations. There are some of these in the patches above 6.1.074, which I just hit enter through. After patching, everything compiled fine and vim works great. (Note: I forgot to mention in my original posting that 6.1.049 will also need to be included, as the compile will fail without it, due to a value that is referenced in patch 6.1.086 was introduced in 6.1.049.)

The previous suggestion of moving /usr/local/include to /usr/include wasn't a satisfactory solution for my setup. I have packages in my /usr/local structure that I don't want mixed in with the /usr structure, which is why they were compiled to install into /usr/local in the first place. :-)

As for the ACCESS VIOLATION issue, did you emerge portage previously? There's a historical issue with gcc-3.1 and portage, which has been fixed recently with the 1.3[a|b] versions of the profile. I use 1.3a and haven't had any problems with ACCESS VIOLATIONs like I did with the 1.2 profile.

Hope that helps,
Will

Lovechild · Posted: Sun Jun 23, 2002 7:19 am Post subject:

ACCESS VIOLATION question:

Well, this is a system built on 1.3a, because the 1.3b tarball wouldn't let me get past the untarring fase without messing up some files, I guess I got a bad tarball downloaded (/me jumps on crappy ISP). But I've previously installed a perfectly good GCC3.1 system on the 1.3a release without this AC problem - I think it has to do with portage 2.x

CowMike · n00b Joined: 16 May 2002 Posts: 52 Location: Ede, NL

I have the same problem on a 1.3b gcc-3.1-r6 system

All packages are updated to the last available (except portage) now...

karwoski · n00b Joined: 30 Jun 2002 Posts: 16 Location: Columbia, MO

I've seen the same problem on my 1.2 system. I don't know what causes the problem but here's the workaround I used. Check the permissions on /dev/pty/s0 (and s1 and s2) and make note of them. Then do a 'chmod 777 /dev/pty/s*', do your vim emerge and once it's completed change the permissions on the files back to what they were (probably 620). Hopefully that'll do it for you.

mortado · Posted: Thu Jul 04, 2002 9:29 pm Post subject: bug # 3038

Bug 3038 also applies to (the original) vi. According to vi changelog bug has been fixed on vi's side. Now somebody wake up vim maintainer!

More on vim: why not make cscope optional? Make it a new USE variable because for me/most cscope is just bloat.

rac · Posted: Mon Aug 19, 2002 1:11 am Post subject:

GCC3 to Portage & Programming, presumed broken ebuild.
_________________
For every higher wall, there is a taller ladder

rphillips · Retired Dev Joined: 18 Apr 2002 Posts: 92

vim ebuilds have been updated lately... its possible this has been fixed.

irony · Posted: Wed Oct 30, 2002 3:46 am Post subject: that's a negative ghostrider...

I just ran into this problem after doing an emerge rsync, emerge vim. It worked fine the first time I emerged it, a month or two ago, but I unmerged it for whatever reason, and when I try to emerge it now, I get the same error.
What is /dev/pty/s*?
_________________
"and if rain brings winds of change, let it rain on us forever..."

barlavento · n00b Joined: 21 Oct 2002 Posts: 1

irony · Posted: Sat Nov 09, 2002 4:19 am Post subject:

I was getting this error logged in as root.
_________________
"and if rain brings winds of change, let it rain on us forever..."

zeek · Posted: Mon Dec 16, 2002 7:28 pm Post subject: still broken

vim still broken:

useofweapons · n00b Joined: 09 Jan 2003 Posts: 26

I just had this problem and got around it with