Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
VIM 6.1-r7 compile failure
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
Lovechild
Advocate
Advocate


Joined: 17 May 2002
Posts: 2858
Location: Århus, Denmark

PostPosted: Sat Jun 22, 2002 11:45 am    Post subject: VIM 6.1-r7 compile failure Reply with quote

Code:

cc1: warning: changing search order for system directory "/usr/local/include"
cc1: warning:   as it has already been specified as a non-system directory
In file included from /usr/X11R6/include/X11/Intrinsic.h:64,
                 from gui.h:25,
                 from structs.h:73,
                 from vim.h:1327,
                 from buffer.c:29:
/usr/include/string.h:42: conflicting types for `memmove'
auto/osdef.h:56: previous declaration of `memmove'
/usr/include/string.h:273: conflicting types for `strcasecmp'
auto/osdef.h:74: previous declaration of `strcasecmp'
/usr/include/string.h:277: conflicting types for `strncasecmp'
auto/osdef.h:77: previous declaration of `strncasecmp'
In file included from /usr/include/bits/string2.h:1185,
                 from /usr/include/string.h:360,
                 from /usr/X11R6/include/X11/Intrinsic.h:64,
                 from gui.h:25,
                 from structs.h:73,
                 from vim.h:1327,
                 from buffer.c:29:
/usr/include/stdlib.h:527: conflicting types for `malloc'
auto/osdef.h:122: previous declaration of `malloc'
make[1]: *** [objects/buffer.o] Error 1
make[1]: Leaving directory `/var/tmp/portage/vim-6.1-r7/work/vim61/src'
make: *** [first] Error 2

!!! ERROR: The ebuild did not complete successfully.
!!! Function src_compile, Line 135, Exitcode 2
!!! gvim make failed

--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-vim-6.1-r7-3117.log"

chmod:     /dev/pty/s0
--------------------------------------------------------------------------------
!!! emerge aborting on  /usr/portage/app-editors/vim/vim-6.1-r7.ebuild .


Anyone have a workaround for this one, I need my vim fix :)
Back to top
View user's profile Send private message
Federkern
n00b
n00b


Joined: 22 Jun 2002
Posts: 1

PostPosted: Sat Jun 22, 2002 4:14 pm    Post subject: Reply with quote

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

Federkern
Back to top
View user's profile Send private message
Lovechild
Advocate
Advocate


Joined: 17 May 2002
Posts: 2858
Location: Århus, Denmark

PostPosted: Sat Jun 22, 2002 4:25 pm    Post subject: Reply with quote

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..
Back to top
View user's profile Send private message
Lovechild
Advocate
Advocate


Joined: 17 May 2002
Posts: 2858
Location: Århus, Denmark

PostPosted: Sat Jun 22, 2002 6:09 pm    Post subject: Reply with quote

Sadly that wasn't the end of it..

Code:

gzipping man page: /var/tmp/portage/vim-6.1-r7/image//usr/share/man/man1/vimtutor.1
gzipping man page: /var/tmp/portage/vim-6.1-r7/image//usr/share/man/man1/xxd.1
strip:
/var/tmp/portage/vim-6.1-r7/image/usr/bin/vim
/var/tmp/portage/vim-6.1-r7/image/usr/bin/xxd
/var/tmp/portage/vim-6.1-r7/image/usr/bin/gvim
>>> Completed installing into /var/tmp/portage/vim-6.1-r7/image/

--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-vim-6.1-r7-26427.log"

chmod:     /dev/pty/s0
chmod:     /dev/pty/s0
--------------------------------------------------------------------------------
!!! emerge aborting on  /usr/portage/app-editors/vim/vim-6.1-r7.ebuild .


This happens regardless of compilation settings
Back to top
View user's profile Send private message
wont-i
n00b
n00b


Joined: 06 Jun 2002
Posts: 8

PostPosted: Sun Jun 23, 2002 5:42 am    Post subject: Reply with quote

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
Back to top
View user's profile Send private message
Lovechild
Advocate
Advocate


Joined: 17 May 2002
Posts: 2858
Location: Århus, Denmark

PostPosted: Sun Jun 23, 2002 7:19 am    Post subject: Reply with quote

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
Back to top
View user's profile Send private message
CowMike
n00b
n00b


Joined: 16 May 2002
Posts: 52
Location: Ede, NL

PostPosted: Sat Jun 29, 2002 6:39 pm    Post subject: Reply with quote

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... :(
Back to top
View user's profile Send private message
karwoski
n00b
n00b


Joined: 30 Jun 2002
Posts: 16
Location: Columbia, MO

PostPosted: Sun Jun 30, 2002 4:12 am    Post subject: Reply with quote

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.
Back to top
View user's profile Send private message
mortado
n00b
n00b


Joined: 02 Jul 2002
Posts: 11
Location: Helsinki, Finland

PostPosted: Thu Jul 04, 2002 9:29 pm    Post subject: bug # 3038 Reply with quote

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.
Back to top
View user's profile Send private message
rac
Bodhisattva
Bodhisattva


Joined: 30 May 2002
Posts: 6553
Location: Japanifornia

PostPosted: Mon Aug 19, 2002 1:11 am    Post subject: Reply with quote

GCC3 to Portage & Programming, presumed broken ebuild.
_________________
For every higher wall, there is a taller ladder
Back to top
View user's profile Send private message
rphillips
Retired Dev
Retired Dev


Joined: 18 Apr 2002
Posts: 92

PostPosted: Mon Aug 19, 2002 3:09 am    Post subject: Reply with quote

vim ebuilds have been updated lately... its possible this has been fixed.
Back to top
View user's profile Send private message
irony
Tux's lil' helper
Tux's lil' helper


Joined: 10 Jul 2002
Posts: 129
Location: CT

PostPosted: Wed Oct 30, 2002 3:46 am    Post subject: that's a negative ghostrider... Reply with quote

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..."
Back to top
View user's profile Send private message
barlavento
n00b
n00b


Joined: 21 Oct 2002
Posts: 1

PostPosted: Sat Nov 09, 2002 2:55 am    Post subject: Reply with quote

Quote:
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).


An alternative is to login as root and then emerge - sudo won't do :D
Back to top
View user's profile Send private message
irony
Tux's lil' helper
Tux's lil' helper


Joined: 10 Jul 2002
Posts: 129
Location: CT

PostPosted: Sat Nov 09, 2002 4:19 am    Post subject: Reply with quote

I was getting this error logged in as root.
_________________
"and if rain brings winds of change, let it rain on us forever..."
Back to top
View user's profile Send private message
zeek
Guru
Guru


Joined: 16 Nov 2002
Posts: 478
Location: Bantayan Island

PostPosted: Mon Dec 16, 2002 7:28 pm    Post subject: still broken Reply with quote

vim still broken:
Code:

gzipping man page: /var/tmp/portage/vim-core-6.1-r2/image//usr/share/man/man1/vim.1
gzipping man page: /var/tmp/portage/vim-core-6.1-r2/image//usr/share/man/man1/xxd.1
gzipping man page: /var/tmp/portage/vim-core-6.1-r2/image//usr/share/man/man1/vimdiff.1
gzipping man page: /var/tmp/portage/vim-core-6.1-r2/image//usr/share/man/man1/vimtutor.1
gzipping man page: /var/tmp/portage/vim-core-6.1-r2/image//usr/share/man/man1/evim.1
strip:
/var/tmp/portage/vim-core-6.1-r2/image/usr/bin/xxd
>>> Completed installing into /var/tmp/portage/vim-core-6.1-r2/image/

--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-vim-core-6.1-r2-11304.log"

chmod:     /dev/pty/s3
--------------------------------------------------------------------------------
Back to top
View user's profile Send private message
useofweapons
n00b
n00b


Joined: 09 Jan 2003
Posts: 26

PostPosted: Thu Jan 09, 2003 11:44 am    Post subject: Reply with quote

I just had this problem and got around it with

Code:
chmod 666 /dev/pty/s0
emerge vim


And it worked. Hope this helps
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum