Tony wrote:
> Yeah, I see similar errors in Big and Normal, but not in Huge, Small
> and Tiny, as follows. My Huge build is the only one with +terminal:
>
> linux-2iyu:~/.build/vim/vim-hg/src/shadow-big # (make || echo 'exit
> status' $? ; date) 2>&1 |tee -a make.log
> gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread
> -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include
> -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo
> -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/libpng16
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0
> -I/usr/include/harfbuzz -I/usr/include/pango-1.0
> -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include
> -I/usr/include/freetype2 -O2 -fno-strength-reduce -Wall -D_REENTRANT
> -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/evalfunc.o
> evalfunc.c
> evalfunc.c:919:6: error: ‘f_term_getansicolors’ undeclared here (not
> in a function); did you mean ‘term_get_bg_color’?
> f_term_getansicolors
> ^~~~~~~~~~~~~~~~~~~~
> term_get_bg_color
> evalfunc.c:938:6: error: ‘f_term_setansicolors’ undeclared here (not
> in a function); did you mean ‘f_term_getansicolors’?
> f_term_setansicolors
> ^~~~~~~~~~~~~~~~~~~~
> f_term_getansicolors
> make: *** [Makefile:3166: objects/evalfunc.o] Error 1
> exit status 2
> Thu 26 Mar 23:13:54 CET 2020
> linux-2iyu:~/.build/vim/vim-hg/src/shadow-big #
Fixed by patch 8.2.0460.
--
f y cn rd ths thn y cn hv grt jb n cmptr prgrmmng
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/202003271124.02RBOv2c012377%40masaka.moolenaar.net.