Hi,
Sorry, my bad! When I have unhooked my environment and fell back to the default
Python Framework for 2.7, the build process was still failing.
So I have figured out that something else was wrong, then I decided to look at
that annoying update that has been flashing for a while on my screen's right
corner, and guess what, it turns out to be some major Xcode update :) So I have
installed that, and it is all fixed now.
MacVim builds against my custom Python2.7 and against my custom Lua. So
everything is working now!
But that error was so similar (maybe even %100 same) to the issue that many
people have experienced before. So I thought that something is broken. Sorry
about that.
Thanks.
On Wednesday, May 21, 2014 10:46:23 PM UTC+1, Muhittin Bilginer wrote:
> Hi,
>
> First of all apologies, I might have already posted this under the original
> topic so sorry if this is a double post. But I am new to Google Groups so I
> was not sure if the post was successful or not.
>
> So here it is again:
>
> I am trying to build MacVim (macvim-snapshot-73 which should be 7.4.258?)
> against my custom Python 2.7 Framework which is installed in
> "/me/apps/Darwin64/python2.7.6-clang-500.2.79"
>
> I am using the following command:
> ./configure --prefix=/me/apps/Darwin64/macvim-7.4-snapshot-73-clang-500.2.79 \
> --with-features=huge \
> --enable-rubyinterp \
> --enable-pythoninterp \
> --enable-perlinterp \
> --enable-cscope \
> --enable-luainterp \
> --with-lua-prefix=/me/apps/Darwin64/lua-5.2.3-clang-500.2.79/bin/lua
>
> I have tried with:
> --with-python-config-dir=/me/apps/Darwin64/python2.7/lib/python2.7/config \
>
> and even:
> --enable-pythoninterp=dynamic \
>
> or:
> --enable-pythoninterp \
>
> Every time I check the log, I can see this problem:
>
> configure:6003: result: no
> configure:6014: checking if compile and link flags for Python are sane
> configure:6031: gcc -o conftest -g -O2
> -I/me/apps/Darwin64/python2.7.6-clang-500.2.79/include/python2.7
> -DPYTHON_HOME='"/me/apps/Darwin64/python2.7.6-clang-500.2.79"'
> -DMACOS_X_UNIX conftest.c -framework Python >&5
> ld: framework not found Python
> clang: error: linker command failed with exit code 1 (use -v to see
> invocation)
> configure:6031: $? = 1
> configure: failed program was:
> | /* confdefs.h */
> | #define PACKAGE_NAME ""
> | #define PACKAGE_TARNAME ""
> | #define PACKAGE_VERSION ""
> | #define PACKAGE_STRING ""
> | #define PACKAGE_BUGREPORT ""
> | #define PACKAGE_URL ""
> | #define UNIX 1
> | #define STDC_HEADERS 1
> | #define HAVE_SYS_WAIT_H 1
> | #define HAVE_SYS_TYPES_H 1
> | #define HAVE_SYS_STAT_H 1
> | #define HAVE_STDLIB_H 1
> | #define HAVE_STRING_H 1
> | #define HAVE_MEMORY_H 1
> | #define HAVE_STRINGS_H 1
> | #define HAVE_INTTYPES_H 1
> | #define HAVE_STDINT_H 1
> | #define HAVE_UNISTD_H 1
> | #define HAVE_AVAILABILITYMACROS_H 1
> | #define FEAT_HUGE 1
> | #define USE_XSMP_INTERACT 1
> | #define FEAT_PERL 1
> | /* end confdefs.h. */
> |
> | int
> | main ()
> | {
> |
> | ;
> | return 0;
> | }
> configure:6035: result: no: PYTHON DISABLED
>
> I know that this has been discussed before in this group, and when I have
> checked the previous progress on this, I have noticed that all the diffs etc.
> they are already implemented in the current configure script. So not sure
> what else I can do to fix this problem.
>
> Could you please help me with this.
>
> Thank you very much.
--
--
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.
