Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 113511 - vim cant find syntaxfile because of wrong path( VIMRUNTIME )
Summary: vim cant find syntaxfile because of wrong path( VIMRUNTIME )
Status: VERIFIED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: AMD64 Linux
: High minor (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-24 14:05 UTC by sam Fischer
Modified: 2005-11-26 13:55 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sam Fischer 2005-11-24 14:05:52 UTC
after emergeing  app-editors/vim-6.4
vim tries to open /usr/share/vim/syntax/syntax.vim which fails as the file is
actually located in /usr/share/vim/vim64/syntax/
highlighting for eg. .bashrc doesnt work

Reproducible: Always
Steps to Reproduce:
1. emerge app-editors/vim
2. edit a file with vim

Actual Results:  
vim gives the following warning

Error detected while processing /etc/vim/vimrc:
line   87:
E484: Can't open file /usr/share/vim/syntax/syntax.vim
Hit ENTER or type command to continue


Expected Results:  
editing should start without warning and highlighting should work


root: ~ # emerge info
Portage 2.0.53_rc7 (default-linux/amd64/2005.0, gcc-3.4.4, glibc-2.3.5-r3,
2.6.14-gentoo-r2-wonderland x86_64)
=================================================================
System uname: 2.6.14-gentoo-r2-wonderland x86_64 AMD Athlon(tm) 64 Processor 3000+
Gentoo Base System version 1.12.0_pre10
dev-lang/python:     2.3.5, 2.4.2
sys-apps/sandbox:    1.2.13
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.20-r1
virtual/os-headers:  2.6.11-r3
ACCEPT_KEYWORDS="amd64 ~amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=k8 -pipe -O2 -fomit-frame-pointer -msse2 -m3dnow -ftracer
-mfpmath=sse"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/lib64/mozilla/defaults/pref /usr/share/config
/var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=k8 -pipe -O2 -fomit-frame-pointer -msse2 -m3dnow -ftracer
-mfpmath=sse"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/linux/distributions/gentoo"
LANG="de_DE@euro"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 X aalib alsa audiofile avi bash-completion berkdb bitmap-fonts bzip2
cdr crypt cups curl eds emboss emul-linux-x86 encode esd exif expat fam ffmpeg
flac foomaticdb fortran gif glut gnome gpm gstreamer gtk gtk2 idn imlib ipv6
java javascript jpeg lcms ldap lzw lzw-tiff mad mng mozilla mp3 mpeg ncurses nls
nvidia opengl oss pam pcre pdflib perl png postgres python qt quicktime readline
sdl spell ssl tcpd tiff truetype truetype-fonts type1-fonts udev usb userlocales
vim-with-x xml2 xmms xpm xv zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY


after reading on bug 107959 I fixed the problem with:
export VIMRUNTIME=/usr/share/vim/vim64/
Comment 1 Ciaran McCreesh 2005-11-24 14:10:54 UTC
What exact versions of vim, vim-core and gvim do you have?
Comment 2 sam Fischer 2005-11-26 09:05:00 UTC
everything updatet to 6.4
Comment 3 Ciaran McCreesh 2005-11-26 09:09:54 UTC
If all your Vim versions are the same, you shouldn't be setting VIM_RUNTIME at
all.  (And if all your Vim versions aren't the same, you should make them the same.)
Comment 4 Ciaran McCreesh 2005-11-26 09:10:00 UTC
If all your Vim versions are the same, you shouldn't be setting VIM_RUNTIME at
all.  (And if all your Vim versions aren't the same, you should make them the same.)
Comment 5 sam Fischer 2005-11-26 13:55:09 UTC
sorry, I was wrong about my vim version