Python 3.8 illegal istruction
See original GitHub issueThis is a bit more of a help for others that encounter my same error. Running tensorflow_recommenders with tensorflow 2.5 on python 3.8 kills the interpreter with a Illegal instruction (core dumped) when running import tensorflow_recommenders.
I wasted a bit of time and came up with a solution: match exactly your environment with the one running on colab. In this particular case using python 3.7 fixes the issue.
I’d suggest to state clearly the supported versions on the guides and the readme of this repository (an maybe also in the setup.py that stops at 3.6 ).
Issue Analytics
- State:
- Created 2 years ago
- Comments:21 (6 by maintainers)
Top Results From Across the Web
Illegal instruction (core dumped) for every installed packages ...
I provide /home/su/miniconda3 folder to complete installing miniconda3. Then I create an environment conda create -n myenv python=3.8. I checked ...
Read more >How to Resolve The Error “Illegal instruction (core dumped ...
How to Resolve The Error “Illegal instruction (core dumped)” when Running “import tensorflow” in a Python Program. 12 Replies.
Read more >Illegal Instruction on install of qiime2-2022.8 - Technical Support
Hi @ebolyen and @thermokarst , I have faced the similar problem as described by Illegal Instruction on on install of qiime2-2022.8.
Read more >Illegal instruction (core image recorded) - Rasa Open Source
Project created in fedora 35 pyenv python 3.8.10 How to solve this problem . Illegal instruction (core image recorded)
Read more >" Illegal instruction (core dumped)" Xavier
Troubles installing Matplotlib on Nano with Python 3.7/3.8 (and a virtual env) ... Sudo python3 setup.py install : Illegal instruction.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

ScaNN 1.2.8 was recently released and doesn’t assume AVX2 support; we now compile with
-mavxrather than-mavx2, and do runtime dispatch to AVX2, when supported, for the important routines. Hopefully this helps.Thanks for debugging–I think the issue is that
vpbroadcastqis an AVX2 instruction, which Sandy Bridge doesn’t support. We will look into compiling the ScaNN wheels the next release without the-mavx2flag so that this issue is resolved. You can try compiling ScaNN yourself without that flag in the meantime to see if that fixes the problem.