Problem with Leopard
davidmorr opened this issue · 7 comments
I tried the latest version (0.4.2) with Leopard (10.5.8). It seemed to open, but nothing ever appeared in the menu bar and disks would still mount.
Version 0.4.1 does still work.
Very useful utility. Has been quite handy recovering a damaged USB flash drive. Thanks.
Are you using a PPC machine? I removed the PPC architecture in the 0.4.2 release, which was a bit arbitrary in hindsight. Apple is making it difficult to support older machines and operating systems with current developer tools. I don't recall if it was actually necessary to remove PPC yet, but I think it will be in the next version of Xcode. If there is interest, I could look into forking the project.
However, 0.4.1 should work the same as 0.4.2 for you. The main reason for 0.4.2 was to sign the executable for GateKeeper.
Are you using a PPC machine? I removed the PPC architecture in the
0.4.2 release, which was a bit arbitrary in hindsight. Apple is
making it difficult to support older machines and operating systems
with current developer tools. I don't recall if it was actually
necessary to remove PPC yet, but I think it will be in the next
version of Xcode. If there is interest, I could look into forking
the project.
I think if people are using PPC machines, then an older version would
probably be sufficiently functional for them.
However, 0.4.1 should work the same as 0.4.2 for you. The main
reason for 0.4.2 was to sign the executable for GateKeeper.
It was on a 24" iMac, Intel CPU. I'm happy to do some testing if you wish.
Cheers
David
Sorry for the delay, I finally got a test machine set up. There is a problem with the 64-bit build in that it depends on "blocks", which were introduced in Snow Leopard (10.6). I'm not sure what triggered that, because there is no use of blocks in the project code, and I reviewed all the changes since 0.4.1 to be sure. I suspect that either the compiler changed or a different compiler was selected. But, there is a work-around: select the application, Get Info for it, then check the "32-bit" checkbox.
I recall that there were some pains with the transition to 64-bit and that Snow Leopard made it easier/more practical for developers, but I don't recall details. Given that the audience is small, I suspect I won't fix this issue as long as the 32-bit work-around is acceptable.
Date: Sun, 19 May 2013 18:58:45 -0700
Mime-Version: 1.0
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-ID: 51998355a69c0_71a754dddc5414a@worker4.rs.github.com.mailSorry for the delay, I finally got a test machine set up. There is a
problem with the 64-bit build in that it depends on "blocks", which
were introduced in Snow Leopard (10.6). I'm not sure what triggered
that, because there is no use of blocks in the project code, and I
reviewed all the changes since 0.4.1 to be sure. I suspect that
either the compiler changed or a different compiler was selected.
But, there is a work-around: select the application, Get Info for
it, then check the "32-bit" checkbox.I recall that there were some pains with the transition to 64-bit
and that Snow Leopard made it easier/more practical for developers,
but I don't recall details. Given that the audience is small, I
suspect I won't fix this issue as long as the 32-bit work-around is
acceptable.
No, that sounds ok to me. Just need to warn people I suppose.
Thanks for looking into it. Disk Arbitrator is a great tool for
dealing with damaged disks.
Cheers
David
From an Intel Mac with OS 10.5.8, terminal shows the following which may help someone fix v0.4.2 for os10.5.8 without needing the 32-bit work-around.
++++
bash-3.2$ /Applications/Disk\ Arbitrator.app/Contents/MacOS/Disk\ Arbitrator
dyld: Symbol not found: __NSConcreteGlobalBlock
Referenced from: /Applications/Disk Arbitrator.app/Contents/MacOS/Disk Arbitrator
Expected in: /usr/lib/libSystem.B.dylib
Trace/BPT trap
++++
I hope this helps.
Great tool.
s
Looks like this might be fixable by doing what Sparkle did:
sparkle-project/Sparkle@d138f64
I tested briefly on 10.5 but the only system I have access to is 32-bit. However, I just released an 0.5 version, and for that I disabled the 64-bit version from running on 10.5, so this issue should be resolved.