“Raise RuntimeError('Not supported on 32-bit Windows')” when installing pyarrow - apache-spark

I get this error whenever I try to install pyarrow in my pc, it is 64bit so I dont understand it:
raise RuntimeError('Not supported on 32-bit Windows')
RuntimeError: Not supported on 32-bit Windows
----------------------------------------
ERROR: Failed building wheel for pyarrow
ERROR: Could not build wheels for pyarrow which use PEP 517 and cannot be installed directly
I have pip updated and have installed many more packages without problems.

The reason PyArrow is trying to build a 32-bit version is certainly that you are using a 32-bit Python installation.
A 64-bit Python installation would probably show you something like this when you run the interpreter prompt (note the "MSC v.1915 64 bit (AMD64)" which indicates it's a 64-bit version):
c:\>python
Python 3.7.2 (default, Jan 2 2019, 17:07:39) [MSC v.1915 64 bit (AMD64)]
Type "help", "copyright", "credits" or "license" for more information.
>>>

Related

Cupy doesnt install with conda on w10-64bits

I am trying to install Cupy using "conda install -c anaconda cupy " with Python 3.7.3 [MSC v.1915 64 bit (AMD64)] :: Anaconda custom (64-bit) on win32
but hangs for hours using several Gb of memory and saying solving environment and nothing happens...
btw i'm using w10 64 bits
Regards

why does anaconda use Apple gcc?

I installed Anaconda python 3.52.
I installed gcc with
brew install gcc
This results in gcc-6 symlinked in /usr/local/bin
My PATH has /usr/local/bin before /usr/bin
Issuing python in terminal gives
Python 3.5.2 |Anaconda 4.1.1 (x86_64)| (default, Jul 2 2016, 17:52:12)
[GCC 4.2.1 Compatible Apple LLVM 4.2 (clang-425.0.28)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>>
Why does anaconda use the 'old' gcc?
Should I create this symlink in /usr/local/bin
ln -s /usr/local/Cellar/gcc/6.1.0/bin/gcc-6 /usr/local/bin/gcc
or is there a better solution?
That information line is not showing you what Python is going to use as a compiler, it is showing what compiler the Python interpreter itself was built with.
We build it with this compiler for maximal compatibility with old versions of OS X.
As you may see Anaconda is using Clang and not GCC
Seems you are working on MacOS where is Clang is default compiler.
First of all : Try to update your Xcode/Clang you are using pretty old version (based on these logs)
Also you may try to change path in your PATH

Why would running 32 bit executeable on 64 bit FreeBSD v8.1 give ELF error?

I have a 32 bit build on FreeBSD v8.1 and attempt to run it on a 64 bit FreeBSD v8.1 and it fails:
[si-fbsd8x64b ~] flume --version
ELF interpreter /libexec/ld-elf.so.1 not found
Abort trap: 6
Can this work, if so, what change do I need to make to enable it?
Install lib32 part of distribution.
ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/8.1-RELEASE/lib32/

Error running ipython notebook on 64 bit

When I am running ipython-notebook. Already install ipython and ipython notebook.
Ubuntu version : 14.04 with 64 Bit
When I run ipython, its running while running ipython-notebook, it shows error:
OSError: /usr/local/lib/python2.7/dist-packages/zmq/libsodium.so: wrong ELF class: ELFCLASS32
I know the error. Error is that I am running 32 bit ipython into 64 bit. Can anyone help me to sort out this problem. Or any idea to substituting ipython 32 bit to 64 bit.
You have a mixture of 32 & 64 bit applications & libraries installed, easiest is to simply un-install iPython 64 bit and install the 32 bit.
Since you already have python installed you should (re)install ipython with:
sudo pip uninstall pyzmq ipython
you will need to enter your password
sudo pip install "ipython[notebook]"
Do not skip re-building zmq
If you really need 64 bit either un-install all of python and install 64 bit from scratch - hopefully all the libraries you need will be available as 64 bit - or look into using python virtual-env to keep your installations discrete.

Is there a way to convert .so using the new ELF ABI to the old

I build a product on a recent Ubuntu version and pack an executable and a shared lib.
3.2.0-48-generic #74-Ubuntu SMP Thu Jun 6 19:43:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 12.04.2 LTS
Release: 12.04
Codename: precise
My .so file return :
ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked, not stripped
When I unpack and try my product on an old debian (2.6.26-2-amd64 ... Now 2010 ... x86_64) I got the following error :
ELF file OS ABI Invalid
I picked the info file of a .so I found on that old debian and get:
ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, stripped
Is there a tool to convert a binary from the new ABI version 1 (GNU/Linux) to the old SYSV ? Or which is the best options to be able to deliver product for both system (Debian 5 / Debian 12) ?

Resources