lucene-pylucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andi Vajda <va...@apache.org>
Subject Re: Building jcc 3.0 under linux / anaconda python
Date Sat, 15 Apr 2017 02:17:28 GMT

On Sat, 15 Apr 2017, Petrus Hyvönen wrote:

> Hi,
>
> First, again - many thanks to all of you who made jcc work with python 3,
> this is a great thing!
>
> Now playing with linux building and I am using anaconda python distribution
> and it seems like the link library for python is called libpython3.6m.so
> instead of the libpython3.6 that other python seems to use and setup.py
> assume. I have another called libpython3.
>
> If I remove this extra_links_args it seems to build fine, as well as if I
> add a "m" to the end:
>
>       elif platform == 'linux':
>            #kwds["extra_link_args"] = \
>            #    lflags + ['-lpython%s.%s' %(sys.version_info[0:2])]
>            kwds["force_shared"] = True    # requires jcc/patches/patch.43
>
> The -m seems to indicate how python was built:
> http://stackoverflow.com/questions/16675865/difference-between-python3-and-python3m-executables
>
> Not sure if there is a danger in removing this, as long as it builds fine?

If it builds and runs fine, it should be good.
This 'm' suffix business on linux adds to the fun (!) of configuring jcc for 
shared mode. Sorry this wasn't improved, there are just too many ways to 
skin this cat now.

Andi..

>
> Best Regards
> /Petrus
>
>
>
>
>
>
> -- 
> _____________________________________________
> Petrus Hyvönen, Uppsala, Sweden
> Mobile Phone/SMS:+46 73 803 19 00
>
Mime
  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message