Richard Hartmann wrote:
> Hi all, > > building vim_extended with the code checker patch fails: > > > % git checkout -b local/code_checking origin/vim > % git merge origin/code_checking > % ./configure --with-features=huge --enable-multibyte --enable-cscope \ > --enable-perlinterp --enable-pythoninterp --enable-rubyinterp \ > --prefix=/usr/local/vim_extended > % make > Starting make in the src directory. > If there are problems, cd to the src directory and run make there > cd src && make first > make[1]: Entering directory > `/home/richih/work/git/vim_extended--playground/src' > mkdir objects > CC="gcc -Iproto -DHAVE_CONFIG_H " srcdir=. sh ./osdef.sh > gcc -c -I. -Iproto -DHAVE_CONFIG_H -g -O2 -D_FORTIFY_SOURCE=1 > -o objects/buffer.o buffer.c > gcc -c -I. -Iproto -DHAVE_CONFIG_H -g -O2 -D_FORTIFY_SOURCE=1 > -o objects/charset.o charset.c > gcc -c -I. -Iproto -DHAVE_CONFIG_H -g -O2 -D_FORTIFY_SOURCE=1 > -o objects/code_check.o code_check.c > code_check.c: In function 'cc_slave_sroutine': > code_check.c:315: error: 'gui' undeclared (first use in this function) > code_check.c:315: error: (Each undeclared identifier is reported only once > code_check.c:315: error: for each function it appears in.) > code_check.c: In function 'cc_update_screen': > code_check.c:364: error: 'gui' undeclared (first use in this function) > code_check.c: In function 'cc_compile_tmp_copy': > code_check.c:500: warning: ignoring return value of 'system', declared > with attribute warn_unused_result > code_check.c: In function 'cc_create_tmp_copy': > code_check.c:520: warning: ignoring return value of 'system', declared > with attribute warn_unused_result > make[1]: *** [objects/code_check.o] Error 1 > make[1]: Leaving directory > `/home/richih/work/git/vim_extended--playground/src' > make: *** [first] Error 2 > % > > Bram, is it OK if we hijack this list for that stuff? I think it makes > sense to keep it here, but if you prefer, we can move it off this list. > > Markus, please put the attached file into the git repo. It's fine to discuss this here. Is this a problem in code_checking or in vim_extended? In the first case you should send a message to Birgi Tamersoy. I'm not sure he reads this list. -- There are 10 kinds of people: Those who understand binary and those who don't. /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ download, build and distribute -- http://www.A-A-P.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
