Is the latest (cutting edge) version of textmate intended to run on a PPC? After updating it today, textmate gives me a "You cannot open the application "TextMate" because it is not supported on this architecture" message on my PowerPC G5 (3.1) when I try to open it.
Kyle Johnson
I am having the same "You can't open the application "TextMate.app" because it is not supported on this architecture."
The installation is under with 10.5.8 on a Dual 2 GHz PowerPC G5.
If it makes any difference, the TextMate update ran while I was logged in as a standard user account. At some point in the process though, I was asked to enter Administrator credentials.
Ever since then, TextMate is dead on this machine.
On Nov 16, 2010, at 8:15 PM, Tony Dew wrote:
I am having the same "You can't open the application "TextMate.app" because it is not supported on this architecture."
The installation is under with 10.5.8 on a Dual 2 GHz PowerPC G5.
If it makes any difference, the TextMate update ran while I was logged in as a standard user account. At some point in the process though, I was asked to enter Administrator credentials.
Ever since then, TextMate is dead on this machine.
Sorry we had the intel only build up for about 30 minutes by accident, re-downloading from the website will give you the proper universal build:
Michael Sheets <mummer@...> writes:
Sorry we had the intel only build up for about 30 minutes by accident,
re-downloading from the website will
give you the proper universal build:
Yes, a download and reinstall seems to have fixed the issue. Thanks!
On 26 Jun 2009, at 00:29, Kyle Johnson wrote:
Is the latest (cutting edge) version of textmate intended to run on a PPC? After updating it today, textmate gives me a "You cannot open the application "TextMate" because it is not supported on this architecture" message on my PowerPC G5 (3.1) when I try to open it.
Yes, we still build for PPC.
But for the update before the last one (I think it was) we saw several people report that the “update” pretty much was missing all the files (but folders were created) — maybe something similar happened to you?
I never found the cause of this problem (and it is very puzzling to me, but we do “outsource” (to the OS) the “move” of the new version, so maybe this was a 10.5.6 bug, given that we never saw it before, nor got reports about this for last update (AFAIK) — are you still on 10.5.6?).