Bug 19369 – Errors when vim is started.

• Status: RESOLVED INVALID
• Product: Gentoo Linux

[Description Steve 2003-04-15 13:48:25 UTC]

When ever vim is started I get these errors:
Error detected while processing /usr/share/vim/vim61/syntax/javascript.vim:
line   60:
E412: Not enough arguments: ":highlight link <args>"
Error detected while processing /usr/share/vim/vim61/syntax/html.vim:


Reproducible: Always
Steps to Reproduce:
1.
2.
3.




Portage 2.0.47-r10 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r4)
=================================================================
System uname: 2.4.20-ck5 i686 Pentium II (Klamath)
GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/gentoo "
CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config
/usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config
/usr/share/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR_OVERLAY=""
USE="x86 oss apm avi crypt gif jpeg libg++ mikmod mmx ncurses pdflib png spell
truetype xml2 xv alsa gdbm berkdb slang readline arts svga tcltk postgres X sdl
gpm tcpd pam libwww ssl perl python esd imlib qt kde motif opengl scanner -3dnow
cups -encode -gnome -gtk -java -mpeg -nls oggvorbis -quicktime sse -xmms -zlib"
COMPILER="gcc3"
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=pentium2 -O3 -pipe -mmmx -fforce-addr -funroll-all-loops
-fomit-frame-pointer -frerun-cse-after-loop "
CXXFLAGS="-march=pentium2 -O3 -pipe -mmmx -fforce-addr -funroll-all-loops
-fomit-frame-pointer -frerun-cse-after-loop "
ACCEPT_KEYWORDS="x86"
MAKEOPTS="-j2"
AUTOCLEAN="yes"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
FEATURES="sandbox ccache"

[Comment 1 Heinrich Wendel (RETIRED) 2003-04-15 15:39:29 UTC]

I think this is a bug with some cflags, change them to the standard values and remerge vim.

[Comment 2 Aron Griffis (RETIRED) 2003-04-23 20:54:54 UTC]

I just tested editing an html file with embedded javascript.  It works fine for me without errors.  I agree with Heinrich; this looks like a problem due to over-aggressive cflagging... :-)

Try scaling your CFLAGS back to -march=pentium2 -O2 and see if that does the trick.  If it doesn't, reopen this bug and we'll continue to investigate.

[Comment 3 Ben Love 2003-04-26 01:20:11 UTC]

I can confirm that this error is due to excessive CFLAGing.  I too had this problem (same error messages and all) when using CFLAGS = "-mcpu=athlon-mp -march=athlon-mp -O3 -pipe -finline-functions -fomit-frame-pointer -funroll-loops -funroll-all-loops -fcse-follow-jumps -frerun-cse-after-loop -fstrength-reduce -fexpensive-optimizations"

However, I soon as I bumped it down to CFLAGS="-march=athlon-mp -O2" and re-emerged, all the errors went away.