On 09/05/08 22:14, Markus Heidelberg wrote: > Tony Mechelynck, 09.05.2008: >> On 09/05/08 09:23, Markus Heidelberg wrote: >>> this patch fixes following compiler warning (gcc 4.1.2 on GNU/Linux): >>> warning: missing sentinel in function call >> I'm using gcc 4.2.1 (with +multi_byte) and I don't get this error: See >> attached the errors from my latest full make, corresponding to 7.1.296. >> I know that some of these errors are unavoidable. > > I just noticed that I've had a problem with pkg-config, so gtk-2 wasn't used, > but gtk-1.2. And this part of the code was in the #else path of HAVE_GTK2. The > last reconfig is long time ago, the configure system didn't change for a > while, so the warning occured for the first time.
Ah, that explains it -- my Vim executable is "with GTK2/Gnome GUI". See http://users.skynet.be/antoine.mechelynck/vim/compunix.htm#p1 for most of my configure settings, except for the line export CONF_ARGS='--with-modified-by="Bram Moolenaar (floating point)"' In addition, I have modified feature.h to get -tag_old_static +xterm_save > > Conclusion: it is an avoidable warning. ...but probably not if you compile with GTK1. I know the authors of GTK1 have abandoned all support of it in favour of GTK2, but what about compiling Vim on legacy systems? When I spoke of "unavoidable" warnings, I meant those from the Perl and Python interfaces, at which Bram has thrown his arms in the air, cursing the packages' bad programming practices. > > Markus Best regards, Tony. -- Meeting, n.: An assembly of people coming together to decide what person or department not represented in the room must solve a problem. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
