Richard Palo wrote: > Came across an issue with 'list_remove' on SunOS when building vim with > python, perl and/or ruby, as it conflicts with the definition found in > <sys/list.h>. > > The following snippet is the error encountered (here on pkgsrc current): > > gcc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/include -I/opt/local/include > > -I/opt/local/include/ncurses -O2 -I/usr/include -I/opt/local/include > > -I/opt/local/include/ncurses -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 > > -D_REENTRANT -O2 -pthread -I/opt/local/include -I/usr/include > > -fstack-protector -I/opt/local/include -I/usr/gnu/include > > -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DPERL_USE_SAFE_PUTENV > > -I/opt/local/lib/perl5/5.18.0/i386-solaris-thread-multi/CORE -o > > objects/if_perl.o auto/if_perl.c > > In file included from /usr/include/sys/vnode.h:53:0, > > from > > /var/tmp/pkgsrc/editors/vim-share/work/.buildlink/lib/perl5/5.18.0/i386-solaris-thread-multi/CORE/perl.h:1519, > > from if_perl.xs:53: > > /usr/include/sys/list.h:47:6: error: conflicting types for 'list_remove' > > In file included from ./proto.h:82:0, > > from ./vim.h:1953, > > from if_perl.xs:38: > > proto/eval.pro:62:6: note: previous declaration of 'list_remove' was here > > The following patchset seems to get over this redefinition: > Index: patches/patch-eval.c
Thanks for the patch. -- In a world without walls and borders, who needs windows and gates? /// 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]. For more options, visit https://groups.google.com/d/optout.
