When building gvim or vim 7.0_alpha20051127 the build breaks with the following errors: i686-pc-linux-gnu-gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -march=i686 -fomit-frame-pointer -pipe -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/lib/perl5/5.8.7/i686-linux/ ORE -I/usr/include/python2.4 -pthread -I/usr/include long -I/usr/lib/ruby/1.8/i686-linux -o objects/eval.o eval.c i686-pc-linux-gnu-gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -march=i686 -fomit-frame-pointer -pipe -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/lib/perl5/5.8.7/i686-linux/ ORE -I/usr/include/python2.4 -pthread -I/usr/include long -I/usr/lib/ruby/1.8/i686-linux -o objects/ex_cmds.o ex_cmds.c i686-pc-linux-gnu-gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -march=i686 -fomit-frame-pointer -pipe -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/lib/perl5/5.8.7/i686-linux/ ORE -I/usr/include/python2.4 -pthread -I/usr/include long -I/usr/lib/ruby/1.8/i686-linux -o objects/ex_cmds2.o ex_cmds2.c i686-pc-linux-gnu-gcc: long: No such file or directory i686-pc-linux-gnu-gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -march=i686 -fomit-frame-pointer -pipe -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/lib/perl5/5.8.7/i686-linux/ ORE -I/usr/include/python2.4 -pthread -I/usr/include long -I/usr/lib/ruby/1.8/i686-linux -o objects/ex_docmd.o ex_docmd.c i686-pc-linux-gnu-gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -march=i686 -fomit-frame-pointer -pipe -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/lib/perl5/5.8.7/i686-linux/ ORE -I/usr/include/python2.4 -pthread -I/usr/include long -I/usr/lib/ruby/1.8/i686-linux -o objects/ex_eval.o ex_eval.c i686-pc-linux-gnu-gcc: long: No such file or directory i686-pc-linux-gnu-gcc: long: No such file or directory i686-pc-linux-gnu-gcc: long: No such file or directory i686-pc-linux-gnu-gcc: long: No such file or directory i686-pc-linux-gnu-gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -march=i686 -fomit-frame-pointer -pipe -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/lib/perl5/5.8.7/i686-linux/ ORE -I/usr/include/python2.4 -pthread -I/usr/include long -I/usr/lib/ruby/1.8/i686-linux -o objects/ex_getln.o ex_getln.c i686-pc-linux-gnu-gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -march=i686 -fomit-frame-pointer -pipe -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/lib/perl5/5.8.7/i686-linux/ ORE -I/usr/include/python2.4 -pthread -I/usr/include long -I/usr/lib/ruby/1.8/i686-linux -o objects/fileio.o fileio.c i686-pc-linux-gnu-gcc: long: No such file or directory i686-pc-linux-gnu-gcc: long: No such file or directory i686-pc-linux-gnu-gcc: long: No such file or directory i686-pc-linux-gnu-gcc: long: No such file or directory make[1]: *** [objects/digraph.o] Error 1 make[1]: *** Waiting for unfinished jobs.... make[1]: *** [objects/charset.o] Error 1 make[1]: *** [objects/ex_eval.o] Error 1 make[1]: *** [objects/diff.o] Error 1 make[1]: *** [objects/ex_cmds.o] Error 1 make[1]: *** [objects/ex_getln.o] Error 1 make[1]: *** [objects/ex_cmds2.o] Error 1 make[1]: *** [objects/edit.o] Error 1 make[1]: *** [objects/fileio.o] Error 1 make[1]: *** [objects/buffer.o] Error 1 make[1]: *** [objects/ex_docmd.o] Error 1 make[1]: *** [objects/eval.o] Error 1 Reproducible: Always Steps to Reproduce:
Do you have USE=tcltk? If so, does turning it off fix this?
I do have that USE flag set, but disabling it still causes the error. So, taking out tcltk I have the following USE flags: USE="X gtk2 gnome esd alsa mbox imap -slang mailwrapper tetex qt dvd spell apache2 gd svg gif truetype mono" Any one else I should disable?
Hrm. I guess it could be any of perl, python or ruby that's doing it. There was a similar bug with tcltk whereby tclConfig.sh would output -Dsomething="long long", which confused the configure script.
So should I enable perl, python, and ruby support for vim? If so, how?
Nope, disable. It looks like you're getting USE="perl python ruby" either from the profile or from use.defaults.
i hit this bug removing tcltk use flag allowed vim to compile gvim is having some access voliation now which im trying to track down ill file a bug when i have an idea of what is going on [ebuild R ] app-editors/vim-7.0_alpha20051127 -acl -bash-completion -cscope -gpm -minimal (-mzscheme) +nls +perl +python -ruby -tcltk -vim-pager -vim-with-x 0 kB
hm, I guess when I tried to turn off "tcltk" it didn't really do it, sorry, my fault. Yes, building with that flag off fixed the vim build. but now gvim dies with a sandbox error :( If you want, I'll create a new bug for that one. As to if you want to close this one or not, I'll leave it up to you.
Yup, a separate bug for the sandbox error please. As for the tcltk thing... We used to have a rather nasty patch for it which fixed configure.in, but it only worked with GNU sed. Upstream recently applied a different patch which was supposed to fix the issue, but clearly it's not quite right. So... Could you please attach your /usr/lib*/tclConfig.sh?
Created attachment 73806 [details] tclConfig.sh file
Created attachment 73852 [details, diff] 035_all_vim-7.0-tcl-backslash-lovin.patch Does this fix it?
Ciaran: fixed it for me.
Fixed in 20051207.
