[chirp_devel] MacOS script change
Hi Gerrit,
Jay just reported that he hasn't been able to launch the MacOS .app since the 8/25 build, which I assume is a result of your script change. I'm embarrassed to say I didn't test it, as it takes a bit of doing for me to get access to a MacOS machine.
Did you test your changed version on a machine with my runtime instead of a vanilla macports?
Thanks!
Dan,
just vanilla macport, what error message did he got?
Gerrit.
On 27 aug 2011, at 20:13, Dan Smith wrote:
Hi Gerrit,
Jay just reported that he hasn't been able to launch the MacOS .app since the 8/25 build, which I assume is a result of your script change. I'm embarrassed to say I didn't test it, as it takes a bit of doing for me to get access to a MacOS machine.
Did you test your changed version on a machine with my runtime instead of a vanilla macports?
Thanks!
-- Dan Smith www.danplanet.com KK7DS
Dan,
BTW, the script changed in 8/26 not 8/25. But I see already whats wrong. Please change in line 45: RUNPYTHON="/opt/kk7ds/bin/python25"; to: RUNPYTHON="/opt/kk7ds/bin/python2.5";
I'm sorry for this, its my mistake,
73's, Gerrit, PA3BYA
On 27 aug 2011, at 20:24, Gerrit Polder wrote:
Dan,
just vanilla macport, what error message did he got?
Gerrit.
On 27 aug 2011, at 20:13, Dan Smith wrote:
Hi Gerrit,
Jay just reported that he hasn't been able to launch the MacOS .app since the 8/25 build, which I assume is a result of your script change. I'm embarrassed to say I didn't test it, as it takes a bit of doing for me to get access to a MacOS machine.
Did you test your changed version on a machine with my runtime instead of a vanilla macports?
Thanks!
-- Dan Smith www.danplanet.com KK7DS
BTW, the script changed in 8/26 not 8/25.
Right, 8/25 was the last one he was able to run, IIRC.
Please change in line 45: RUNPYTHON="/opt/kk7ds/bin/python25"; to: RUNPYTHON="/opt/kk7ds/bin/python2.5";
Okay, changed.
Jay, can you report back tomorrow and let me know that it's fixed?
Thanks!
So, tried changing line 45 as below. No luck. Comes up and says this is the first time you're running, click OK, then get a Failed to run CHIRP.
While looking at the script, I see that you're trying to make MacPorts python 2.7 install work, so I go ahead and add the missing libs I had for my py27 install.
That works, dunno what makes the script fail with the static py25 install.
So, for those folks not using MacPorts without all of the needed python modules and instead using that KK7 static install stuff... they'll likely still be non-functional. Will try the next daily as well, though will have to hack the script a bit to force it to use the static install and see if it is still nonfunctional.
Jay
On Sat, Aug 27, 2011 at 4:16 PM, Dan Smith dsmith@danplanet.com wrote:
BTW, the script changed in 8/26 not 8/25.
Right, 8/25 was the last one he was able to run, IIRC.
Please change in line 45: RUNPYTHON="/opt/kk7ds/bin/**
python25"; to: RUNPYTHON="/opt/kk7ds/bin/**python2.5";
Okay, changed.
Jay, can you report back tomorrow and let me know that it's fixed?
Thanks!
-- Dan Smith www.danplanet.com KK7DS
While looking at the script, I see that you're trying to make MacPorts python 2.7 install work, so I go ahead and add the missing libs I had for my py27 install.
Maybe this is because the script sees that you had py27 installed, but failed to determine that you didn't have all the required libs? Hopefully that means someone with just the runtime installed would be okay.
What libs did you install? That would help Gerrit fix up that logic I think.
On Sun, Aug 28, 2011 at 1:25 PM, Dan Smith dsmith@danplanet.com wrote:
Maybe this is because the script sees that you had py27 installed, but failed to determine that you didn't have all the required libs? Hopefully that means someone with just the runtime installed would be okay.
What libs did you install? That would help Gerrit fix up that logic I think.
No message at first, just failed to run. In that case python2.7 is present, but none of the other three files are present. I do NOT get a message about MacPorts at all in this case.
I installed py27-gtk via macports as this is the first package needed. BTW, py27-libxml2 is a dependency for py27-gtk so it installs automatically, so that installed the second package automatically.
To see what happens when there is a missing macports package, I tried running the 08272011 daily again. This time I got a "Macport py27-serial module is not installed" message as expected and THEN a Failed to Run message.
Installed py27-serial, and everything came right up.
Not sure why I wasn't getting a "The Macport py27-gtk module for OSX is not installed".
Oh wait! Actually I do know why I think... that message is being created with GTK, not straight X11.... and at that time there is no GTK yet. Likely need to use xmessage and not ERRMSG.
Jay
Jay, Dan,
the script didn't work properly when both Dan's python and macports python (partially) are installed. I changed it now such that Dan's python is preferred, when that is not installed it checks for the macports version and its installed components.
Please find enclosed the fixed script. ERRMESG is not a command, just a variable.
Gerrit.
On 28 aug 2011, at 19:36, Jay Moran wrote:
On Sun, Aug 28, 2011 at 1:25 PM, Dan Smith dsmith@danplanet.com wrote: Maybe this is because the script sees that you had py27 installed, but failed to determine that you didn't have all the required libs? Hopefully that means someone with just the runtime installed would be okay.
What libs did you install? That would help Gerrit fix up that logic I think.
No message at first, just failed to run. In that case python2.7 is present, but none of the other three files are present. I do NOT get a message about MacPorts at all in this case.
I installed py27-gtk via macports as this is the first package needed. BTW, py27-libxml2 is a dependency for py27-gtk so it installs automatically, so that installed the second package automatically.
To see what happens when there is a missing macports package, I tried running the 08272011 daily again. This time I got a "Macport py27-serial module is not installed" message as expected and THEN a Failed to Run message.
Installed py27-serial, and everything came right up.
Not sure why I wasn't getting a "The Macport py27-gtk module for OSX is not installed".
Oh wait! Actually I do know why I think... that message is being created with GTK, not straight X11.... and at that time there is no GTK yet. Likely need to use xmessage and not ERRMSG.
Jay
On Mon, Aug 29, 2011 at 6:02 AM, Gerrit Polder pa3bya@amsat.org wrote:
the script didn't work properly when both Dan's python and macports python (partially) are installed. I changed it now such that Dan's python is preferred, when that is not installed it checks for the macports version and its installed components.
Please find enclosed the fixed script.
Cool. So, remove the KK7DS py25 stuff... then remove py27-serial to test the one, then py27-gtk to test to make sure the message is thrown it sounds like.
ERRMESG is not a command, just a variable.
Ahhh, that's what I get for not paying more attention.
It was a different type of message box with a octagon stop sign that said ERROR or STOP in it when py27-serial wasn't installed, very different han the smallish black and white message box for the other messages -- like the "failed to run" message I ALSO got after the stop sign message.
No message at all for py27-gtk not being installed and just the "failed to run" message in the smallish box. Must be the way xmessage is called then? Or observer error on my part? Probably need to test with py27-gtk missing and macports py2.7 preferred though just to make sure.
Jay
Jay,
did you get those errors with the new script????? checking of python and the modules needed is done by the bash script and missing modules are reported by xmessage.
with the previous version the check was not done properly resulting in python 2.7 starting without the needed modules. The error message you got was from python.
but as I said already this should be fixed with the new script.
Gerrit.
On 29 aug 2011, at 12:27, Jay Moran wrote:
On Mon, Aug 29, 2011 at 6:02 AM, Gerrit Polder pa3bya@amsat.org wrote: the script didn't work properly when both Dan's python and macports python (partially) are installed. I changed it now such that Dan's python is preferred, when that is not installed it checks for the macports version and its installed components.
Please find enclosed the fixed script.
Cool. So, remove the KK7DS py25 stuff... then remove py27-serial to test the one, then py27-gtk to test to make sure the message is thrown it sounds like.
ERRMESG is not a command, just a variable.
Ahhh, that's what I get for not paying more attention.
It was a different type of message box with a octagon stop sign that said ERROR or STOP in it when py27-serial wasn't installed, very different han the smallish black and white message box for the other messages -- like the "failed to run" message I ALSO got after the stop sign message.
No message at all for py27-gtk not being installed and just the "failed to run" message in the smallish box. Must be the way xmessage is called then? Or observer error on my part? Probably need to test with py27-gtk missing and macports py2.7 preferred though just to make sure.
Jay
participants (4)
-
Dan Smith -
Gerrit Polder -
Gerrit Polder -
Jay Moran