Hi list, This patch is relevant only to those who build Vim with Python on Mac OS X under the option —disable-darwin.
The current configure script passes to the linker the path to a Python library via a pair of -L and -l flags, and an absolute path to the library as well. This implies that, if there is another Python in linker search paths, and if it is not the same one specified by the absolute path, the linker will come across two different Python libraries. Surprisingly, the linker is so generous that it won’t complain; it links Vim against two different Python libraries to make an executable for you. Of course, even if a resulting executable doesn’t crash at start and runs normally for a while, nobody can predicts what will happen to it. The proposed patch addresses this issue by removing the -l flag and its argument, so that the linker will rely only on the Python library specified by an absolute path. In addition to that, the patch also removes the flag “-framework CoreFoundation” (Remember, I’m talking about Vim build on Mac OS X under the option —disable-darwin). This flag comes from Python’s config/Makefile and was used when the Python was built. So, it should be irrelevant to Vim build of the present case. Regards, Kazunobu Kuriyama -- -- 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.
configure.in.patch
Description: Binary data
