Thanks a lot. It is working now. SS
On Monday, October 19, 2015 at 11:20:44 AM UTC-7, [email protected] wrote: > > I got the following output: > > julia> ENV["PYTHON"]="python" > "python" > > julia> Pkg.build("PyCall") > INFO: Building PyCall > INFO: PyCall is using python (Python 2.7.3) at /usr/bin/python, libpython > = libpython2.7 > > Thanks, > SS > > On Monday, October 19, 2015 at 11:10:21 AM UTC-7, Steven G. Johnson wrote: >> >> >> >> On Monday, October 19, 2015 at 1:54:01 PM UTC-4, [email protected] >> wrote: >>> >>> Hello, >>> >>> I performed a find for the .so files and I got the following : >>> >>> ./home/sarkar/.julia/v0.4/Conda/deps/usr/lib/libopenblas.so >>> >>> ./home/sarkar/.julia/v0.4/Conda/deps/usr/pkgs/openblas-0.2.14-3/lib/libopenblas.so >>> >>> How do I get libopenblas64_.so within 0.4 version of julia ? >>> >> >> Those are the ones installed by Conda and used within Conda, not Julia's >> libopenblas with the incompatible ABI. So, they are less likely to cause >> trouble. >> >> However, it is odd that it is using Conda at all if you have a system >> Python installed. It only uses Conda if the system Python wasn't working. >> What happens if you do >> >> ENV["PYTHON"]="python" >> Pkg.build("PyCall") >> >> to force it to use the system's python (/usr/bin/python) again? >> >
