Updates:
Status: Fixed
Comment #3 on issue 366 by chrisbr...@googlemail.com: compilation problems
on yosemite
https://code.google.com/p/vim/issues/detail?id=366
Closing
--
You received this message because this project is configured to send all
issue notifications to this address.
Comment #2 on issue 366 by ctrud...@arsensa.com: compilation problems on
yosemite
https://code.google.com/p/vim/issues/detail?id=366
I just grabbed whatever was in the downloads directory as I don't have
Mecurial installed on this machine. By the looks of it, it is just 7.4.
Feel free t
Comment #1 on issue 366 by ht.mtche...@gmail.com: compilation problems on
yosemite
https://code.google.com/p/vim/issues/detail?id=366
What version of the product are you using? On what operating system?
Vim 7.4
OS X 10.10.3
If 7.4 meant 7.4.000, it's too old.
Use 7.4.062 or later, at whic
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 366 by ctrud...@arsensa.com: compilation problems on yosemite
https://code.google.com/p/vim/issues/detail?id=366
What steps will reproduce the problem?
1. ./configure --prefix=/usr/local --disable-darwin --enable-gui=no
2. mak
On Thursday, December 20, 2012 4:47:11 PM UTC-8, James McCoy wrote:
> On Thu, Dec 20, 2012 at 03:02:59PM -0500, joe M wrote:
>
> > On Thu, Dec 20, 2012 at 1:49 PM, joe M wrote:
>
> > > Hello,
>
> > >
>
> > > The latest mercurial version of vim fails with the below error. python
>
> > > --vers
On Thu, Dec 20, 2012 at 03:02:59PM -0500, joe M wrote:
> On Thu, Dec 20, 2012 at 1:49 PM, joe M wrote:
> > Hello,
> >
> > The latest mercurial version of vim fails with the below error. python
> > --version == 2.7.3
> >
> > gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -pipe -ftracer
> > -fgcse-after
Hello,
The latest mercurial version of vim fails with the below error. python
--version == 2.7.3
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -pipe -ftracer
-fgcse-after-reload -march=corei7-avx -mcx16 -msahf -mno-movbe
-mno-aes -mpclmul -mpopcnt -mno-abm -mno-lwp -mno-fma -mno-fma4
-mno-xop -mno-b
On Thu, Dec 20, 2012 at 1:49 PM, joe M wrote:
> Hello,
>
> The latest mercurial version of vim fails with the below error. python
> --version == 2.7.3
>
> gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -pipe -ftracer
> -fgcse-after-reload -march=corei7-avx -mcx16 -msahf -mno-movbe
> -mno-aes -mpclmul
On Friday, 13 April 2012 00:57:34 UTC+8, Senthil Kumaran wrote:
> ./configure --enable-pythoninterp --with-features=huge
> --with-python-config-dir=/home/senthil/localpython/lib/python2.7/config
I solved it -
http://stackoverflow.com/questions/10059539/compiling-vim-with-python-support-on-ub
return
> os.path.join(get_path('platstdlib').replace("/usr/local","/usr",1), "config"
> + (sys.pydebug and "_d" or ""), "Makefile")
> AttributeError: 'module' object has no attribute 'pydebug'
Hello
On Monday, 9 April 2012 19:17:17 UTC+8, Senthil Kumaran wrote:
> That's a useful clue. I have the source of Python and I see that those
> modules defined Module/config.c in the Python source. Instead of pointing to
> source, I pointed to default install of Python from Ubuntu. Perhaps some
> pro
On Monday, 9 April 2012 13:10:45 UTC+8, JohnBeckett wrote:
> src/Makefile includes:
> objects/py_config.o: $(PYTHON_CONFDIR)/config.c
>
> The file /usr/lib/python2.7/config/config.c does not contain any
> of the identifiers that give the errors above, so my guess is
> that you have a mixture
Senthil Kumaran wrote:
> I am trying to compile vim from source with python
> interpreter on Ubuntu. I have installed the dependencies for
> vim, installed python2.7-devel and python2.7-dbg packages on
> Ubuntu and do the configure step like this
>
> ./configure --enable-pythoninterp
> --with-p
This one seems tricky, because I tried every suggestion on www. I could do any
experiment which could be helpful to compile vim with python interpreter
support.
I am trying to compile vim from source with python interpreter on Ubuntu. I
have installed the dependencies for vim, installed python
14 matches
Mail list logo
