-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FAISS on Raspberry Pi #1071
Comments
I am quite pessimistic about the possibility to compile with a 32 bit arch. Can you compile with -m64 ? |
Trying to do Any idea of what kind of changes I would need to do to make it work with 32 bit arch? What does the |
SWIGWORDSIZE32 is probably a flag needed for SWIG. My point is that it might be easier to set up a compile chain in 64 bits than to port Faiss to 32 bits. |
We compiled successfully on 64-bit Linux on Raspberry Pi. |
If you feel like it, please share as much info as possible here on how to compile for Raspberry Pi. |
I'm hitting the same error when trying to install faiss on a raspberry pi, with |
We compiled FAISS successfully on Raspberry Pi 4B and integrated it into Milvus: https://github.com/milvus-io/milvus/tree/aarch64 Platform information: Main change is about compiling option. Detailed change please refer to: milvus-io/milvus@651b122 |
Excellent! Thanks. |
Hi, Can't Faiss run on 32-bit ARMV7? |
Summary
Installing FAISS for python (from source) on raspberry pi throws an error:
Makefile:22: recipe for target 'swigfaiss.o' failed
The above error is thrown after a long list of errors, the first of which is:
swigfaiss.cpp:3348:3: error: #error "SWIG wrapped code invalid in 32 bit architecture, regenerate code using -DSWIGWORDSIZE32"
I have also attached the complete log.txt.
Any help would be appreciated.
Platform
Raspberry Pi 3B+
OS: Raspbian
Running on:
Interface:
Reproduction instructions
./configure --without-cuda
(configuration file successfully recognizes python)make -j4 & make install
(Successfully compiles and installs)make -C python
(throws error)The text was updated successfully, but these errors were encountered: