First, if CHIRP won’t launch & won't run, you may have neglected to install the Python runtime. CHIRP needs that. Even though Mac OS X includes Python built-in, the runtime has to be installed is because it includes PyGTK and some other libraries that Chirp requires, in addition to Python itself: http://www.d-rats.com/download/OSX_Runtime/

Second, CHIRP is an application, which runs in its own application window. CHIRP is not designed to run from a command window. You run CHIRP by clicking in the application: chirp-4.0.0.app. You can run CHIRP from any folder, but it is advisable to deploy the chirp-4.0.0.app into the Applications folder and run it from there. I keep CHIRP in in my Dock where it is convenient to open.

Pete


On May 18, 2014, at 8:36 PM, Jerald Josephs <jerald.josephs@gmail.com> wrote:

Hello,

I just discovered Chirp yesterday and I downloaded it to check it out. I read the entire FAQ at http://chirp.danplanet.com/projects/chirp/wiki/FAQ, but there is nothing there about the application not starting up.

I have an early 2011 MacBook Pro 17 with 16GB RAM, running Mac OS X 10.9 with all software up-to-date. After downloading the ZIP, I dragged Chirp over to the Applications folder.

I then opened Chirp and went down into .../Applications/chirp-4.0.0/Contents/MacOS and ran "chirp" from there in a Terminal window. This is what I got:

$ ./chirp
./chirp: line 15: /opt/kk7ds/bin/python2.7: No such file or directory
./chirp: line 15: exec: /opt/kk7ds/bin/python2.7: cannot execute: No such file or directory

But, I do have python:

$ python -V
Python 2.7.5
$ which python
/usr/bin/python

T
​he Chirp shell script is setting PYTHON

PYTHON=/opt/kk7ds//Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python

If I search my disk from /Library, this is what I find:

rary root# cd /
jerald-mbp-wlan:/ root# find /Library -name Python -print
/Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Versions/A/Resources/Python
/Library/Frameworks/Python.framework/Python
/Library/Frameworks/Python.framework/Versions/3.3/Python
/Library/Frameworks/Python.framework/Versions/3.3/Resources/Python.app/Contents/MacOS/Python
/Library/Python

It's interesting to see that I have a framework for Python 3.3 and yet the binary in my path is v2.7.5

Not sure what I should do next.

BR,
Jerald​

_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users