On Fri, Jun 16, 2006 at 10:37:37AM +0200, Stefano Zacchiroli wrote: > tags 373890 + moreinfo > thanks > > On Fri, Jun 16, 2006 at 09:45:48AM +0300, Torok Edwin wrote: > > Package: vim > > Version: 1:7.0-017+6 > > Severity: normal > > > > On amd64 vim has no support for cscope (:cs says sorry this command is not > > available in this version). > > Comparing :version from the 64-bit env, and the 32-bit chroot: I see > > the amd64 version has -cscope, while the 32bit one has +cscope. Why is > > that? Shouldn't these settings be consistent through architectures? > > Well, that's not consistent with the output you quote in the bugreport. Oops, I pasted the same :version output to both 64 and 32. The output from 32 bit env is: Big version with GTK2-GNOME GUI. Features included (+) or not (-): +arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset +cindent +clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments +cryptv +cscope +cursorshape +dialog_con_gui +diff +digraphs +dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path +folding -footer +fork() +gettext -hangul_input +iconv +insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap +menu +mksession +modify_fname +mouse +mouseshape +mouse_dec +mouse_gpm -mouse_jsbterm +mouse_netterm +mouse_xterm +multi_byte +multi_lang -mzscheme +netbeans_intg -osfiletype +path_extra +perl +postscript +printer -profile +python +quickfix +reltime +rightleft +ruby +scrollbind +signs +smartindent -sniff +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white +tcl +terminfo +termresponse +textobjects +title +toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup +X11 -xfontset +xim +xsmp_interact +xterm_clipboard -xterm_sav
> Let's see: > > > from 64 bit env: > > Normal version with GTK2 GUI. Features included (+) or not (-): > <snip> > > -cscope > > > In 32 bit env: > > Normal version with GTK2 GUI. Features included (+) or not (-): > > -cscope > > Which variant of vim are you running? You can discover it either with > "readline -f `which vim`". If you're running vim-tiny the behvaiour you > report is normal, vim-tiny has no support for cscope, while all other > variants should have it. I am using vim.full in both environments: [EMAIL PROTECTED]:~$ dpkg-architecture DEB_BUILD_ARCH=amd64 DEB_BUILD_ARCH_OS=linux DEB_BUILD_ARCH_CPU=amd64 DEB_BUILD_GNU_CPU=x86_64 DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_BUILD_GNU_TYPE=x86_64-linux-gnu DEB_HOST_ARCH=amd64 DEB_HOST_ARCH_OS=linux DEB_HOST_ARCH_CPU=amd64 DEB_HOST_GNU_CPU=x86_64 DEB_HOST_GNU_SYSTEM=linux-gnu DEB_HOST_GNU_TYPE=x86_64-linux-gnu [EMAIL PROTECTED]:~$ readlink -f `which vim` /usr/bin/vim.full [EMAIL PROTECTED]:~$ dchroot -d "readlink -f `which vim`" (ia32) readlink -f /usr/bin/vim /usr/bin/vim.full Thanks for the quick reply. Cheers, Edwin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
