Feature #8469

Support for Apple's new M1 System on a Chip Architecture

Added by Brian Jalet over 1 year ago. Updated over 1 year ago.

Status:Closed Start date:11/23/2020
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:-
Chirp Version:daily Model affected:(All models)

Description

The subject line speaks for itself really. I do know from the documentation that CHIRP is only supported on the Intel architecture today, but I was hoping there might be plans on the roadmap to build in support for this new chip. I've upgraded to the Apple Macbook Air M1 architecture and it is incredible. But I didn't think ahead to realize the M1 was not supported.

Thanks for your consideration.


Related issues

duplicates Bug #8639: Mac M1 Chip Closed 01/02/2021

History

Updated by Who Cares over 1 year ago

+1 for this one and get it fixed.

after some troubleshooting, it looks like it simply requires a re-compilation and it should be running fine.

Using package embedded Python leads to a killed process:

> bash -x CHIRP.app/Contents/MacOS/chirp
++ dirname CHIRP.app/Contents/MacOS/chirp
+ LOCATION=CHIRP.app/Contents/MacOS
+ PYTHON=CHIRP.app/Contents/MacOS/../CHIRP
+ export PYTHONPATH=/Library/Python/2.7/site-packages:CHIRP.app/Contents/MacOS/../Resources/site-packages:.
+ PYTHONPATH=/Library/Python/2.7/site-packages:CHIRP.app/Contents/MacOS/../Resources/site-packages:.
+ export DYLD_FALLBACK_LIBRARY_PATH=CHIRP.app/Contents/MacOS/../Resources/lib:/opt/homebrew/lib/
+ DYLD_FALLBACK_LIBRARY_PATH=CHIRP.app/Contents/MacOS/../Resources/lib:/opt/homebrew/lib/
+ export DYLD_VERSIONED_LIBRARY_PATH=CHIRP.app/Contents/MacOS/../Resources/lib:/opt/homebrew/lib/
+ DYLD_VERSIONED_LIBRARY_PATH=CHIRP.app/Contents/MacOS/../Resources/lib:/opt/homebrew/lib/
+ exec CHIRP.app/Contents/MacOS/../CHIRP CHIRP.app/Contents/MacOS/../Resources/chirp/chirpw
Killed: 9

Changing the script to use the system python fails with not found library (didn't realize there is a hard-coded dependency on it):

> bash -x CHIRP.app/Contents/MacOS/chirp
++ dirname CHIRP.app/Contents/MacOS/chirp
+ LOCATION=CHIRP.app/Contents/MacOS
+ PYTHON=CHIRP.app/Contents/MacOS/../CHIRP
+ export PYTHONPATH=/Library/Python/2.7/site-packages:CHIRP.app/Contents/MacOS/../Resources/site-packages:.
+ PYTHONPATH=/Library/Python/2.7/site-packages:CHIRP.app/Contents/MacOS/../Resources/site-packages:.
+ export DYLD_FALLBACK_LIBRARY_PATH=CHIRP.app/Contents/MacOS/../Resources/lib:/opt/homebrew/lib/
+ DYLD_FALLBACK_LIBRARY_PATH=CHIRP.app/Contents/MacOS/../Resources/lib:/opt/homebrew/lib/
+ export DYLD_VERSIONED_LIBRARY_PATH=CHIRP.app/Contents/MacOS/../Resources/lib:/opt/homebrew/lib/
+ DYLD_VERSIONED_LIBRARY_PATH=CHIRP.app/Contents/MacOS/../Resources/lib:/opt/homebrew/lib/
+ /usr/bin/arch -x86_64 /usr/bin/python CHIRP.app/Contents/MacOS/../Resources/chirp/chirpw
Traceback (most recent call last):
  File "CHIRP.app/Contents/MacOS/../Resources/chirp/chirpw", line 24, in <module>
    from chirp.drivers import *
  File "CHIRP.app/Contents/Resources/chirp/chirp/drivers/anytone_iii.py", line 33, in <module>
    from chirp.ui.memdetail import MemoryDetailEditor
  File "CHIRP.app/Contents/Resources/chirp/chirp/ui/memdetail.py", line 16, in <module>
    import gtk
  File "CHIRP.app/Contents/Resources/site-packages/gtk/__init__.py", line 30, in <module>
    import gobject as _gobject
  File "CHIRP.app/Contents/Resources/site-packages/gobject/__init__.py", line 26, in <module>
    from glib import spawn_async, idle_add, timeout_add, timeout_add_seconds, \
  File "CHIRP.app/Contents/Resources/site-packages/glib/__init__.py", line 22, in <module>
    from glib._glib import *
ImportError: dlopen(CHIRP.app/Contents/Resources/site-packages/glib/_glib.so, 2): Library not loaded: /usr/local/opt/glib/lib/libgobject-2.0.0.dylib
  Referenced from: CHIRP.app/Contents/Resources/site-packages/glib/_glib.so
  Reason: image not found

I guess, installing x64 version of Homebrew might solve the problem, but I don't really want to keep two versions of Homebrew.

Updated by Bernhard Hailer over 1 year ago

  • Status changed from New to Closed

Duplicates #8639. That ticket might offer a solution for you. If it doesn't, please follow and post there. Thanks!

Updated by Brian Jalet over 1 year ago

Unfortunately, the referenced #8639 doesn't solve the problem for me.

Also available in: Atom PDF