Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
View attachment 1910451

SSD works fine. My testing Mac runs with an m.2-to-PATA adapter.

It’s the protocol negotiation you need to be aware of.

If you’re on a PATA bus Mac, the adapter renders the m.2 or mSATA SSD as a PATA/IDE drive (as seen by the Mac). That’s what you see above.

For SATA bus Macs, such as the G5s, the trick is the m2-to-2.5" adapter needs to be able to auto-negotiate to SATA I/II speeds. In my experience, current m.2-to-SATA adapters tend to do fairly well with this. It’s what I use with an earlier MacBook Pro.

The challenge here is that some SATA 2.5-inch SSDs, especially earlier SATA III SSD models, will only work at SATA III speeds and will not auto-negotiate down to SATA II or SATA I on a slower SATA bus (generally, SATA II will work without trouble on a SATA I bus). When this happens, your SATA Mac will not boot from that drive (or will have a very difficult time doing so). This was an issue I had with a 2011-vintage 2.5-inch SATA III SSD and my G5. At the time, I chose to buy an older, SATA II SSD as the workaround and I traded the SATA III drive to someone who needed it. Were I to replace that SATA II SSD nowadays, I’d probably get an m.2 SSD and buy another m.2-to-SATA adapter, as this solution is pretty cheap these days. These adapters tend to work pretty well, and the on-board circuitry in these adapters appear to auto-negotiate in the presence of a slower protocol bus (either that, or else the auto-negotiation is happening at the m.2 controller).



I use the TextEdit bundled with 10.5.8, and it’s one of the few applications from 10.5.8 I’ve found which works just fine in the 10A96 setting.

When I can get to a moment when I can do so, I’ll test the TextEdit in 10A190 but in the 10A96 environment.
If the 10A190 version doesn’t work, please try my build. If neither work, you can try building yourself from within 10A096 as the project is included in the examples folder for Xcode.

Unfortunately the version included with 10A432 is intel only.
 
  • Like
Reactions: B S Magnet
I was using 10A190, but since then I haven't managed to get TextEdit from Leopard to work at all even after correcting permissions, so it must have been a fluke the first time I did it.

Cheers :)

Hugh

I’m guessing you already did this, though if not, trashing the TextEdit preferences and starting on a fresh pref file might make a difference.

Separately, but semi-related, I found there was a preference permissions issue with, of all things, Illustrator CS4, in which the application spontaneously crashed or hung on the splash screen until I changed its preference file permissions to 777. Afterwards, Illustrator is working.

At least with the 10A96 build, I gather there may be some issue (possibly a framework I haven’t figured out yet) tied to the fact that its version of Disk Utility is incomplete and it will not check/verify/fix permissions. The same issue could be related to this by preventing the correct settings for permissions when a new file, such as a pref file, gets generated by an application. Then again, I also have no data supporting this hypothesis and it’s nothing better than speculation.
 
  • Like
Reactions: ChrisCharman
@B S Magnet Could you please test this under 10A096 as i don't have a build imaged to a system at the moment?

I must know… what exactly did you do here? It’s a PowerPC binary, version 1.6, and it works (i.e., it saved a test .rtf), but TextEdit is not part of AOSP. How did you build it? EDIT: n/m I now see what you wrote in a separate post… dang this thread is fire tonight.

EDIT #2: Amazingly, I’ve managed to break Xcode. It no longer will launch, abruptly aborting. This is really interesting. Also, I feel like a dork for never really having looked through the Examples directory before you made mention of it. I’m… sort of mesmerized at the moment. EDIT #3: Ah, I think this is related to my trying to install a newer version of Xcode from the 10A222 or 10A261 source earlier in the week; upon re-install of the Xcode 3.2 in 10A96, the same issue with postflight script in Mac10.4u.sdk fails, so I’m re-installing Xcode, package by package and skipping that one.
 
Last edited:
  • Like
Reactions: ChrisCharman
I must know… what exactly did you do here? It’s a PowerPC binary, version 1.6, and it works (i.e., it saved a test .rtf), but TextEdit is not part of AOSP. How did you build it? EDIT: n/m I now see what you wrote in a separate post… dang this thread is fire tonight.

EDIT #2: Amazingly, I’ve managed to break Xcode. It no longer will launch, abruptly aborting. This is really interesting. Also, I feel like a dork for never really having looked through the Examples directory before you made mention of it. I’m… sort of mesmerized at the moment.
I explored the folder and built this the first time last year and also attempted to build the versions from Lion and Mountain Lion but they require some later frameworks according to my recollection. It’s possible with modifications to the code we could get them working down the line or at least port some features into 1.6 but as I’m focused on parity with 10.6.0 still i set that aside for the moment. It was only when i was looking back through the thread that i realised I hadn’t already shared this with you guys - so i thought i’d offer it up now.
 
  • Like
Reactions: B S Magnet
Are you still having this issue?

Yes, Finder is hopeless, I just quit it on start up.
Screenshot 2021-11-15 13-08-55.png
 
I just replaced ImageIO framework with original one (from 10A190), and both Cmake and Python27 ports built with no issues.


I stupidly did not write down what exactly I modified in R port file last time to force it use gcc7, so now trying to figure it out once again LOL.

After R is upgraded to the latest 4.1.2, I am back to trying RStudio and Stan built. Along that, I wanna build newer gcc to make life a bit easier. If everything with R fails, alternative is Julia.

Okay R 4.1.2 is built.

R-app (basic GUI) fails to compile. If anyone can help with suggestion, please. Log attached.

RStudio (advanced GUI)
is unavailable on MacPorts and building it on its own also fails on configure part with:

Code:
# enable c++11
if(NOT MSVC)
   include(CheckCXXCompilerFlag)
   CHECK_CXX_COMPILER_FLAG("-std=c++11" COMPILER_SUPPORTS_CXX11)
   if(NOT COMPILER_SUPPORTS_CXX11)
      message(FATAL_ERROR "The compiler ${CMAKE_CXX_COMPILER} has no C++11 support. Please use a different C++ compiler.")
   else()
      set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++11")
   endif()
endif()
 

Attachments

  • R-app.log.zip
    26.8 KB · Views: 86
I explored the folder and built this the first time last year and also attempted to build the versions from Lion and Mountain Lion but they require some later frameworks according to my recollection. It’s possible with modifications to the code we could get them working down the line or at least port some features into 1.6 but as I’m focused on parity with 10.6.0 still i set that aside for the moment. It was only when i was looking back through the thread that i realised I hadn’t already shared this with you guys - so i thought i’d offer it up now.

A curious thing in Xcode 3.2 from 10A96 is I found two different “example” project directories for TextEdit.

The first one, at /Developer/Examples/TextEdit, failed to build (with 3 warnings and 5 errors). I noticed this source had 14 source files.

The second one, at /Developer/Examples/AppKit/TextEdit, successfully built (and with no warnings or errors). This one had 13 source files.

Not to leave good enough alone (and also bemused by the irony that the TextEdit 1.6 which shipped with 10A96 won’t save RTF documents but this home-build will)…

1636958395618.png


I would have liked to build it with the same four-language support as Build 10A96 on the whole, but this is good enough for now. :)

Also, it would have been nifty had there been other example projects we could have used.



On an unrelated note: does anyone know where to locate a copy of Resourcerer 2.4.1 (the carbonized OS X version), released back in 2001? It’s not on the garden, which is somewhat surprising. I need a utility like this to view and edit the few, but still important .rsrc resource fork files for components such as Finder.
 
  • Like
Reactions: ChrisCharman
Not sure of its utility, but in addition to the latest R, I also compiled Clang, though an archaic one:

clang.png


GUI for R is a real trouble. R-Commander fails due to some dependencies and also, importantly, XQuartz. I was unable to install the latter either as a standalone update (Leo version fails, SL version fails) or as Xorg-Server port (some dependencies fail).
R-app / Mac-GUI fails both as a port and as Xcode project.
RStudio fails, but some hope for Cmake trickery remains.
At the moment I am out of options here, it seems.
 
  • Like
Reactions: B S Magnet
On an unrelated note: does anyone know where to locate a copy of Resourcerer 2.4.1 (the carbonized OS X version), released back in 2001? It’s not on the garden, which is somewhat surprising. I need a utility like this to view and edit the few, but still important .rsrc resource fork files for components such as Finder.

Try looking on KDX, there is some old software out there. Once you connect to tracker, you get a list of Mac-related servers. Not all of those allow guest downloads, but several do.
 
  • Like
Reactions: B S Magnet
A curious thing in Xcode 3.2 from 10A96 is I found two different “example” project directories for TextEdit.

The first one, at /Developer/Examples/TextEdit, failed to build (with 3 warnings and 5 errors). I noticed this source had 14 source files.

The second one, at /Developer/Examples/AppKit/TextEdit, successfully built (and with no warnings or errors). This one had 13 source files.

Not to leave good enough alone (and also bemused by the irony that the TextEdit 1.6 which shipped with 10A96 won’t save RTF documents but this home-build will)…

View attachment 1910623

I would have liked to build it with the same four-language support as Build 10A96 on the whole, but this is good enough for now. :)

Also, it would have been nifty had there been other example projects we could have used.



On an unrelated note: does anyone know where to locate a copy of Resourcerer 2.4.1 (the carbonized OS X version), released back in 2001? It’s not on the garden, which is somewhat surprising. I need a utility like this to view and edit the few, but still important .rsrc resource fork files for components such as Finder.
I don’t remember seeing the second version of the TextEdit project, i’ll have to take a look.
 
  • Like
Reactions: B S Magnet
What machine are you running this on again and what ‘fixes’ have you applied to your system thus far?

G5 Quad, 10A190

The issue is immediately observed on a clean install (from dmg, I didn't take the pain to apply patches to dvd installer).
It is reproducable: I have reinstalled the same image at least twice.
So you can be sure that it is not a result of any "fixes" from my side. If there is a problem with preinstalled dmg image, that I cannot verify.

I have installed two of your patches and moved some kexts from 10.5.8 (nothing beyond what is in the table, but less than that). Finder issue remained as it was, nothing changed it in any noticeable way.

It is of little concern for me personally, since I almost never use Finder for years. My choice has been Path Finder in its place.

I rather find irritating the dlyb issue that continuously consumes some processor power and prevents permissions fixing. I described it earlier with logs, and from what I understood it's not just me, and there is no fix.
 
Anyone who is good with Xcode, could you please check if R-app can be compiled in it?

As of now, I cannot fix macport, and I don't understand Xcode workings. Choosing target and building for PPC failed.
 
G5 Quad, 10A190

The issue is immediately observed on a clean install (from dmg, I didn't take the pain to apply patches to dvd installer).
It is reproducable: I have reinstalled the same image at least twice.
So you can be sure that it is not a result of any "fixes" from my side. If there is a problem with preinstalled dmg image, that I cannot verify.

I have installed two of your patches and moved some kexts from 10.5.8 (nothing beyond what is in the table, but less than that). Finder issue remained as it was, nothing changed it in any noticeable way.

It is of little concern for me personally, since I almost never use Finder for years. My choice has been Path Finder in its place.

I rather find irritating the dlyb issue that continuously consumes some processor power and prevents permissions fixing. I described it earlier with logs, and from what I understood it's not just me, and there is no fix.
No it’s not an issue caused by a fix, but it’s an issue i no longer have on two of my systems, but probably still on the G5 as I haven’t used that system for a while but the other two are heavily modified at this point so i was just trying to get an understanding of what to suggest based on what you’ve already done. Leave with me.

The LibXML2 installer will have, hopefully, fixed some underlying issues that you wouldn’t have been aware of without analysis of the console, and improved stability.

Yeah the dyld issue i think you’re referencing is another known issue on 10A190 - i’m still working on a fix for that one.

Do you have any issues with Directory Services CPU consumption at all? After i replaced mine with the Leopard version my system is now running at between 2-5% idle currently which is significantly better than it was before.

There are also problems with the filesystem and Disk Utility and it’s supporting components in these builds, which is another todo.
 
I don’t remember seeing the second version of the TextEdit project, i’ll have to take a look.

It is entirely possible that higher-level directory was put there when I tried to install one of the later Xcode 3.2 builds last week. For TextEdit, it seemed to be making calls for CoreVideo-related headers which I don’t think the other version (the one which compiled correctly) had.

Separately, I’m trying another build upload to the garden. When I left it early today, it was uploading. When I returned to it hours later, the upload had completed but upon submitting it, there was an error message requiring contacting the site admin. So I’m trying again in a slightly different way.
 
  • Like
Reactions: ChrisCharman
Minor updates:

I revamped Appendix A in the WikiPost from a long, two-part list to a table. It’s slightly more voluminous for the WikiPost’s total character count (by about a thousand characters), but I’m hoping it’s also more legible at a glance. There are some recent software reports I still need to add, but otherwise, it’s ready. Let me know if you’re having readability issues (i.e., if you have protanopia/deuteranopia/tritanopia) and I’ll see what I can do.

Links to Builds 10A286 (Client) and 10A222 (Server) are up and have been added to Table 1. Kernel Debug Kit for 10A286 is also added. Builds 10A261 (Server), 10A314 (Client), and 10A354 (Client) are queued to be next.
 
Last edited:
Minor updates:

I revamped Appendix A in the WikiPost from a long, two-part list to a table. It’s slightly more voluminous for the WikiPost’s total character count (by about a thousand characters), but I’m hoping it’s also more legible at a glance. There are some recent software reports I still need to add, but otherwise, it’s ready. Let me know if you’re having readability issues (i.e., if you have protanopia/deuteranopia/tritanopia) and I’ll see what I can do.

Links to Builds 10A286 (Client) and 10A222 (Server) are up and have been added to Table 1. Kernel Debug Kit for 10A286 is also added. Builds 10A261 (Server), 10A314 (Client), and 10A354 (Client) are queued to be next.

Thank you very much!

P. S. Perhaps it's worth amending Xcode compatibility in Wiki. It is definitely not true that only 10A96 version of 3.2 work, since I am using 3.2 from 10A190 and it works too. 3.2 from 10A222 also works, but only the app itself. That is, one has to install it first, copy the app, uninstall everything, install 3.2 from 10A190 and use the copied app there. (I have copied the whole Developer folder just in case and keep both.)
 
Thank you very much!

P. S. Perhaps it's worth amending Xcode compatibility in Wiki. It is definitely not true that only 10A96 version of 3.2 work, since I am using 3.2 from 10A190 and it works too. 3.2 from 10A222 also works, but only the app itself. That is, one has to install it first, copy the app, uninstall everything, install 3.2 from 10A190 and use the copied app there. (I have copied the whole Developer folder just in case and keep both.)
That’s interesting. Previous tests proved the 10A190 beta Xcode to be unusable. I will have another look at this when i get the chance to confirm on another system.
 
Minor updates:

I revamped Appendix A in the WikiPost from a long, two-part list to a table. It’s slightly more voluminous for the WikiPost’s total character count (by about a thousand characters), but I’m hoping it’s also more legible at a glance. There are some recent software reports I still need to add, but otherwise, it’s ready. Let me know if you’re having readability issues (i.e., if you have protanopia/deuteranopia/tritanopia) and I’ll see what I can do.

Links to Builds 10A286 (Client) and 10A222 (Server) are up and have been added to Table 1. Kernel Debug Kit for 10A286 is also added. Builds 10A261 (Server), 10A314 (Client), and 10A354 (Client) are queued to be next.
Awesome! Thanks @B S Magnet

Will begin downloading and testing the builds I don’t already have when I return from work! Excellent news!!
 
  • Like
Reactions: B S Magnet
That’s interesting. Previous tests proved the 10A190 beta Xcode to be unusable. I will have another look at this when i get the chance to confirm on another system.

Unusable in which way?

Both Kencu and me used specifically that version, and everything compiles. I cannot verify if every possible function of Xcode app works, since I don’t use it in GUI, but it seems to be working. When I tried building R.app from within Xcode, compilation went through (failed in result, but that’s not Xcode fault).
 
  • Like
Reactions: ChrisCharman
Unusable in which way?

Both Kencu and me used specifically that version, and everything compiles. I cannot verify if every possible function of Xcode app works, since I don’t use it in GUI, but it seems to be working. When I tried building R.app from within Xcode, compilation went through (failed in result, but that’s not Xcode fault).
Yeah it’s the Xcode IDE that’s reported not to work, not the command line tools.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.