James McCoy wrote: > Hi Bram, > > It recently came up[0] that the way Vim builds its Python support makes > it fragile to changes in which modules are builtin to the Python > library. > > When the set of modules that are builtin/extensions differs from what > Vim knew when it was built, it will at best complain that it can't load > the library. At worst, it will crash due to undefined symbols. > > This is due to Vim compiling in the config.c from the Python install > that existed when it was built. Removing that, as the attached patch > does, resolves the issue. > > I've tested this with both --enable-pythoninterp and > --enable-pythoninterp=dynamic.
It appears that when building with both Python and Python3 the config.c was already omitted. So why was it ever included? Was this needed for an older Python versino? -- We are the Borg of GNU GPL. We will assimilate your source code. Resistance is futile. /// 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
