On Σαβ, Φεβ 10, at 10:46 Dan Nicholson wrote:
> On 2/10/07, Ag. Hatzimanikas <[EMAIL PROTECTED]> wrote:
> >
> > All I know (from another source but me,A.J.Mechelynck),is that some
> > warnings are
> > common and unavoidable,such as those that coming when you enable the various
> > interfaces e.g perl and python.
>
> Ag, would you care to give it a shot? I'm in the same position as
> Randy and really know nothing about enabling the various bindings.
> Also, are these warnings or errors? I can never make any sense of the
> output when I run the testsuite in LFS.
>
I was based my words in one mail by Tony in past December.
However,running now the tests,I am not taking any kind of these warnings
( I have linked vim against perl/python and ruby),as far it concerns the
various
scripting languages.
I am taking only the following failure in make test,which apparently is not
worthing to mention at all,(I don't have xorg installed in X11R6).
gcc -c -DHAVE_CONFIsing-prototypes -I/usr/X11R6/include version.c
make: *** [vim] Error 1
Also there are some (harmless,I guess) warnings for undefined variables.
For what is worth I am running these tests under a system with
gcc (GCC) 4.1.2 20070108 (prerelease)
and glibc from cvs
(GNU libc) 2.5.90
but I don't know if that makes a difference,I think not.
My vim --version is:
VIM - Vi IMproved 7.0 (2006 May 7, compiled Feb 10 2007 21:15:36)
Included patches: 1-4, 6-26, 29-31, 33-44, 46-56, 58-64, 66-73, 75-107, 109,
111-115,
117-122, 124-129, 133-137, 139-155, 157-160, 162-169, 172-178
Compiled by ag
Big version with GTK2 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_save
Compiled with:
./configure --with-features=big \
--prefix=/usr \
--disable-netbeans \
--enable-multibyte\
--enable-fontset\
--enable-gui=gtk2 \
--with-vim-name=vim \
--with-x \
--with-compiledby=ag \
--enable-perlinterp \
--enable-rubyinterp \
--enable-pythoninter
The output of the `make test' is really worthing,I believe,only for the vim
developers
and is it safe to assume and maybe mention in the book,that surely (the output)
depends
from the various options that someone enable/disable -and there are a lot of
them.
Some distributions provides,3 or 4 (sometimes) flavors of vim for that same
reason.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
