On Wednesday, June 5, 2013 4:47:43 PM UTC-5, Ben Fritz wrote:
> configure:5452: checking if compile and link flags for Python are sane
> configure:5469: gcc -o conftest -g -O2 
> -I/rfs/proj/cs_ifis_projects/Tools/Python/current/include/python2.7 
> -DPYTHON_HOME=\"/rfs/proj/cs_ifis_projects/Tools/Python/current\"   
> -L/usr/local/lib conftest.c  
> -L/rfs/proj/cs_ifis_projects/Tools/Python/current/lib/python2.7/config 
> -lpython2.7 -lresolv -lsocket -lnsl -lrt -ldl -lpthread -lm >&5
> conftest.c:0: unterminated string or character constant
> conftest.c:0: possible real start of unterminated constant
> configure:5469: $? = 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 FEAT_HUGE 1
> | #define USE_XSMP_INTERACT 1
> | /* end confdefs.h.  */
> | 
> | int
> | main ()
> | {
> | 
> |   ;
> |   return 0;
> | }

The configure script is compiling a simple program, which should never fail to 
compile, and checking to see if it links.

But somehow it is getting compile errors instead.

I copied the file content shown above into a test file, and ran the same gcc 
command, and it compiled fine.

So, I manually edited the configure file again, to remove the compile step and 
make that test always succeed. Now my Vim compiles and --version shows +python. 
:echo has('python') returns 1 and :python print 'hello' works.

There has to be a better way to make this succeed!

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to