Nick Deubert wrote:
> I am on a system where I don't want to affect the installed packages
> so first I successfully built and installed python 2.5 in a directory
> owned by me and kept the build directory around as well. Next I put
> the python bin install directory on my PATH so that it would find it
> use the one I just built instead of the old one on the system. Then I
> configured vim 7.0 with:
> --enable-python-interp --with-python-config-dir=<python build
> directory> and it configured fine:
> checking for python... /home/TOOLS/python-2.5/bin/python
> checking Python version... 2.5
> checking Python is 1.4 or better... yep
> checking Python's install prefix... /home/TOOLS/python-2.5
> checking Python's execution prefix... /home/TOOLS/python-2.5
> checking Python's configuration directory... (cached)
> /home/TOOLS/vim_src/Python-2.5
> checking if -pthread should be used... yes
> checking if compile and link flags for Python are sane... yes
>
> Then when I make vim it gets a good amount compiled before getting:
> gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_ATHENA -DFUNCPROTO=15
> -DNARROWPROTO -g -O2 -I/usr/X11R6/include
> -I/home/TOOLS/python-2.5/include/python2.5 -pthread -o
> objects/if_python.o if_python.c
> make[1]: *** No rule to make target
> `/home/TOOLS/vim_src/Python-2.5/config.c', needed by
> `objects/py_config.o'. Stop.
>
> So I took at look at the Makefile in the Python build directory and
> sure enough there is no rule for config.c but there is:
> Makefile Modules/config.c: Makefile.pre \
> ...
>
> so I tried adding a rule right above it like so:
> config.c: Makefile Modules/config.c
You should not need to build config.c, it should be somewhere in the
Python files. The Vim configure script tries to find it, but perhaps it
was moved between Python 2.4 and 2.5? I haven't tried 2.5 yet.
You can try running configure with the --python-config-dir argument. If
you manage to make it work let us know where the config.c can be found,
so that the configure script can be adjusted.
--
So when I saw the post to comp.editors, I rushed over to the FTP site to
grab it. So I yank apart the tarball, light x candles, where x= the
vim version multiplied by the md5sum of the source divided by the MAC of
my NIC (8A3FA78155A8A1D346C3C4A), put on black robes, dim the lights,
wave a dead chicken over the hard drive, and summon the power of GNU GCC
with the magic words "make config ; make!".
[Jason Spence, compiling Vim 5.0]
/// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ download, build and distribute -- http://www.A-A-P.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
