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.
Looking back over the thousands of posts we have amassed on this thread i see that @Larsvonhier was leeching 10A335 at one point, was this ever uploaded anywhere as we’re still missing that build?

I think @Larsvonhier was probably seeing the same reference to a long-dead magnet as what I’m seeing, though maybe he had success grabbing it in its entirety. It and 10A421(a) are shown in the same place, and both appear long-dormant and probably lost to time.

Two known builds I’ve not seen come up anywhere: 10A335 10A394 and 10A411.
 
Last edited:
  • Like
Reactions: ChrisCharman
I think @Larsvonhier was probably seeing the same reference to a long-dead magnet as what I’m seeing, though maybe he had success grabbing it in its entirety. It and 10A421(a) are shown in the same place, and both appear long-dormant and probably lost to time.

Two known builds I’ve not seen come up anywhere: 10A335 and 10A411.
There are videos for 10A314, 10A335, 10A354, 10A380, 10A394 10A402, 10A411 and 10A421 on YouTube. No working links for the builds we need that i could find unfortunately.
 
  • Like
Reactions: B S Magnet
There are videos for 10A314, 10A335, 10A354, 10A380, 10A394 10A402, 10A411 and 10A421 on YouTube. No working links for the builds we need that i could find unfortunately.

Sorry, I should have been clearer: I haven’t seen sources/magnets/seeds for either of 10A394 or 10A411.

Somewhat in the same realm: I don’t think I’ve run across a 10A190 Server build after all this time. There are plenty of 10A190 Client builds, however. That said, it is not a high priority for me to track down a 10A190 Server build.
 
  • Like
Reactions: ChrisCharman
A quick update on later version of Xcode. Good news, Xcode from 10A261 installed on 10A190 (clean system with no Xcode). Bad news, Xcode app crashes on launch, though it is seen as being executable and attempts to start.

GCC is newer than from Xcode from 10A190.

As a related note: it appears a developer working at Apple at the time noted there being up to three dozen internal builds in which Xcode was broken due to Objective-C-related issues. They are quoted:

“…we would move in giant monolithic releases where every group would just dump in whatever they had ready and the whole thing would get released with nightly builds. With SnowLeopard in particular, I remember three dozen releases in a row where Xcode was unusable due to obj-c garbage collection issues. Random stuff you didn't expect like CoreGraphics would have showstopper issues and then we'd report it and it would get fixed by the next week.”
They go on to describe how fundamentally different post-Snow Leopard development was from Snow Leopard, Leopard, and Tiger, due mainly to the change in Mac Software Engineering VPs and their very different product development approaches — when Bertrand Serlet was replaced by Craig Federrighi in March 2011. The latter is who was behind the “yearly OS” model adopted since Lion (which came with, as the quoted developer described, a more conservative approach — using a “sprint” system instead of nightly builds — that discouraged major features being brought into the OS’s development as quickly).
 
As a related note: it appears a developer working at Apple at the time noted there being up to three dozen internal builds in which Xcode was broken due to Objective-C-related issues. They are quoted:

“…we would move in giant monolithic releases where every group would just dump in whatever they had ready and the whole thing would get released with nightly builds. With SnowLeopard in particular, I remember three dozen releases in a row where Xcode was unusable due to obj-c garbage collection issues. Random stuff you didn't expect like CoreGraphics would have showstopper issues and then we'd report it and it would get fixed by the next week.”
They go on to describe how fundamentally different post-Snow Leopard development was from Snow Leopard, Leopard, and Tiger, due mainly to the change in Mac Software Engineering VPs and their very different product development approaches — when Bertrand Serlet was replaced by Craig Federrighi in March 2011. The latter is who was behind the “yearly OS” model adopted since Lion (which came with, as the quoted developer described, a more conservative approach — using a “sprint” system instead of nightly builds — that discouraged major features being brought into the OS’s development as quickly).

I will try installing Xcode from 10A286 once you upload the OS image.

I asked above but I think to no avail: does anyone know which components Xcode installs outside of its own Developer folder? I want to copy the whole thing every build installs, so that we can move select components under root and see what works.
 
I have tried both. But still did not work.
[automerge]1599852039[/automerge]
I have tried it both. But still didn’t work

Has this been ever solved or SSD do not work with 10.6 PPC as boot drives? I was considering getting one for my Quad, but if they cannot be made to work, that will be a waste.
 
I will try installing Xcode from 10A286 once you upload the OS image.

I asked above but I think to no avail: does anyone know which components Xcode installs outside of its own Developer folder? I want to copy the whole thing every build installs, so that we can move select components under root and see what works.
You could use either pacifist or flat package editor to ascertain where the files are destined to be installed. Off the top of my head some go into /usr also.
 
  • Like
Reactions: barracuda156
You could use either pacifist or flat package editor to ascertain where the files are destined to be installed. Off the top of my head some go into /usr also.

By the way, how to pull updated gcc into older Xcode installation to see if it is functional? Anything beyond replacing the folder itself?

I have now a separate 10A190 installation for silly experiments LOL
 
I would check that the imageIO header is present in the include folder or potentially it could be needed in the apple internal development folder that is only created when ‘make install headers’ is run on certain apple open source projects, particularly the internal development tools which are not installed during a normal Xcode install. If it’s not anywhere on the system, you could check if it’s present on Retail SL or Leopard and then, after reviewing the header for any architecture specific changes you may need to make, copy it to the appropriate location. This is similar to the missing XCRun that needs to be replaced, also TargetConfig etc

Edit: This header should reside in the Application Services Framework first and foremost

UPDATED. I have finally located ImageIO here. How to link it with Macports?

imageio.png


P. S. python27 fails to upgrade for this reason too:

Code:
:info:build /usr/bin/gcc-4.2 -c -fno-strict-aliasing -fno-common -dynamic -pipe -I/opt/local/libexec/openssl11/include -Os -arch ppc -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes  -I. -IInclude -I./Include -I/opt/local/libexec/openssl11/include -I/opt/local/include -I/opt/local/include/db48  -DPy_BUILD_CORE -DPYTHONPATH='":plat-darwin:plat-mac:plat-mac/lib-scriptpackages:lib-tk:lib-old"' \
:info:build         -DPREFIX='"/opt/local/Library/Frameworks/Python.framework/Versions/2.7"' \
:info:build         -DEXEC_PREFIX='"/opt/local/Library/Frameworks/Python.framework/Versions/2.7"' \
:info:build         -DVERSION='"2.7"' \
:info:build         -DVPATH='""' \
:info:build         -o Modules/getpath.o ./Modules/getpath.c
:info:build ./Modules/getpath.c: In function ‘calculate_path’:
:info:build ./Modules/getpath.c:452: warning: ‘NSModuleForSymbol’ is deprecated (declared at /usr/include/mach-o/dyld.h:189)
:info:build ./Modules/getpath.c:452: warning: ‘NSLookupAndBindSymbol’ is deprecated (declared at /usr/include/mach-o/dyld.h:179)
:info:build ./Modules/getpath.c:454: warning: ‘NSLibraryNameForModule’ is deprecated (declared at /usr/include/mach-o/dyld.h:159)
:info:build In file included from /System/Library/Frameworks/Carbon.framework/Headers/Carbon.h:24,
:info:build                  from Include/pymactoolbox.h:10,
:info:build                  from Python/mactoolboxglue.c:27:
:info:build /System/Library/Frameworks/ApplicationServices.framework/Headers/ApplicationServices.h:55:29: error: ImageIO/ImageIO.h: No such file or directory
:info:build /usr/bin/gcc-4.2 -c -fno-strict-aliasing -fno-common -dynamic -pipe -I/opt/local/libexec/openssl11/include -Os -arch ppc -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes  -I. -IInclude -I./Include -I/opt/local/libexec/openssl11/include -I/opt/local/include -I/opt/local/include/db48  -DPy_BUILD_CORE -o Modules/main.o Modules/main.c
:info:build /usr/bin/gcc-4.2 -c -fno-strict-aliasing -fno-common -dynamic -pipe -I/opt/local/libexec/openssl11/include -Os -arch ppc -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes  -I. -IInclude -I./Include -I/opt/local/libexec/openssl11/include -I/opt/local/include -I/opt/local/include/db48  -DPy_BUILD_CORE -o Modules/gcmodule.o Modules/gcmodule.c
:info:build /usr/bin/gcc-4.2 -fno-strict-aliasing -fno-common -dynamic -pipe -I/opt/local/libexec/openssl11/include -Os -arch ppc -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes  -I. -IInclude -I./Include -I/opt/local/libexec/openssl11/include -I/opt/local/include -I/opt/local/include/db48  -DPy_BUILD_CORE  -c ./Modules/threadmodule.c -o Modules/threadmodule.o
:info:build /usr/bin/gcc-4.2 -fno-strict-aliasing -fno-common -dynamic -pipe -I/opt/local/libexec/openssl11/include -Os -arch ppc -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes  -I. -IInclude -I./Include -I/opt/local/libexec/openssl11/include -I/opt/local/include -I/opt/local/include/db48  -DPy_BUILD_CORE  -c ./Modules/signalmodule.c -o Modules/signalmodule.o
:info:build make: *** [Python/mactoolboxglue.o] Error 1
:info:build make: *** Waiting for unfinished jobs....
:info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_python27/python27/work/Python-2.7.18'
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_python27/python27/work/Python-2.7.18" && /usr/bin/make -j4 -w all
:info:build Exit code: 2
:error:build Failed to build python27: command execution failed
:debug:build Error code: CHILDSTATUS 23496 2
:debug:build Backtrace: command execution failed
:debug:build     while executing
:debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring"
:debug:build     invoked from within
:debug:build "command_exec -callback portprogress::target_progress_callback build"
:debug:build     (procedure "portbuild::build_main" line 8)
:debug:build     invoked from within
:debug:build "$procedure $targetname"
:error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_python27/python27/main.log for details.

Notice this in the log: :info:build /System/Library/Frameworks/ApplicationServices.framework/Headers/ApplicationServices.h:55:29: error: ImageIO/ImageIO.h: No such file or directory
 
Last edited:
UPDATED. I have finally located ImageIO here. How to link it with Macports?


Notice this in the log: :info:build /System/Library/Frameworks/ApplicationServices.framework/Headers/ApplicationServices.h:55:29: error: ImageIO/ImageIO.h: No such file or directory

ImageIO.h is missing though.
There are no headers for it, while headers exist for other frameworks there.


Screenshot 2021-11-15 02-27-11.png
 
  • Like
Reactions: ChrisCharman
Hi @Edgecrusherr and @ScreenSavers,

As I mentioed in a previous post you have to replace
the ImageIO.framework inside the ApplicationServices.framework
with the one from Leopard.
That will fix the "crazy" images.
See my porst #149 and #187.

Best regards,
voidRunner

Well, this was the reason everything been failing to build for three days.

ANYONE REPLACING THIS FRAMEWORK KEEP THIS IN MIND.
 
  • Like
Reactions: ChrisCharman
Sorry, I should have been clearer: I haven’t seen sources/magnets/seeds for either of 10A394 or 10A411.

Somewhat in the same realm: I don’t think I’ve run across a 10A190 Server build after all this time. There are plenty of 10A190 Client builds, however. That said, it is not a high priority for me to track down a 10A190 Server build.
Yes, i was wondering if there were server builds for all seeds or not. Most likely there were but fewer people found them interesting or useful enough to archive.
 
By the way, how to pull updated gcc into older Xcode installation to see if it is functional? Anything beyond replacing the folder itself?

I have now a separate 10A190 installation for silly experiments LOL
No idea i’ve not attempted to so that before - maybe a web search will provide some clues?

Yeah i have adopted a similar system of creating disk images so I don’t have to start from scratch if something goes wrong.
 
Place the header where it’s supposed to go and see what happens. Sometimes you only need the header to build not even the frameworks referenced inside the header.

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.
 
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.
So do you have ‘blocky images’ again now? It may be worth trying what I suggested and just moving the header file over into the replaced framework for the best of both worlds.
 
@Hughmac There is a link in the Wiki regarding a fix you mentioned for TextEdit not being able to utilise .rtf files. I can't remember what build you were running when you experienced the issue, can you remember?

On my modified build of 10A190 (TextEdit 1.6 Bundle version 251) this isn't an issue. @barracuda156 are you able to test this on your machine please as you have modified the system to a lesser degree?

Either way, for anybody experiencing problems with the version of TextEdit on their system i have an alternative fix to using the Leopard app (Version 1.5 Bundle Version 244).

Attached to this post is version 1.6 (Bundle version 248) that i have built for PowerPC 10.6. It has been compiled for Snow Leopard but should also run on minimum system version 10.5.

@B S Magnet Could you please test this under 10A096 as i don't have a build imaged to a system at the moment?
 

Attachments

  • TextEdit.zip
    396.4 KB · Views: 84
  • Love
Reactions: B S Magnet
Has this been ever solved or SSD do not work with 10.6 PPC as boot drives? I was considering getting one for my Quad, but if they cannot be made to work, that will be a waste.

1636934655470.png


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).

@Hughmac There is a link in the Wiki regarding a fix you mentioned for TextEdit not being able to utilise .rtf files. I can't remember what build you were running when you experienced the issue, can you remember?

On my modified build of 10A190 (TextEdit 1.6 Bundle version 251) this isn't an issue. @barracuda156 are you able to test this on your machine please as you have modified the system to a lesser degree?

Either way, for anybody experiencing problems with the version of TextEdit on their system i have an alternative fix to using the Leopard app (Version 1.5 Bundle Version 244).

Attached to this post is version 1.6 (Bundle version 248) that i have built for PowerPC 10.6. It has been compiled for Snow Leopard but should also run on minimum system version 10.5.

@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 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.
 
I will try installing Xcode from 10A286 once you upload the OS image.

I’ll post on this thread once I successfully get it uploaded. As with the last time I did so, getting 6–8GB files uploaded without issues onto the garden tends to be a bit finicky.

I asked above but I think to no avail: does anyone know which components Xcode installs outside of its own Developer folder? I want to copy the whole thing every build installs, so that we can move select components under root and see what works.

Possible way to find out:

Open the Xcode installer pkg/mpkg with Pacifist 3.0 in a Leopard environment and view the installation directory tree for all the pkg contents it installs in places like /usr/* and elsewhere. EDIT: @ChrisCharman already addressed this question, n/m.
 
@Hughmac There is a link in the Wiki regarding a fix you mentioned for TextEdit not being able to utilise .rtf files. I can't remember what build you were running when you experienced the issue, can you remember?

On my modified build of 10A190 (TextEdit 1.6 Bundle version 251) this isn't an issue. @barracuda156 are you able to test this on your machine please as you have modified the system to a lesser degree?

Either way, for anybody experiencing problems with the version of TextEdit on their system i have an alternative fix to using the Leopard app (Version 1.5 Bundle Version 244).

Attached to this post is version 1.6 (Bundle version 248) that i have built for PowerPC 10.6. It has been compiled for Snow Leopard but should also run on minimum system version 10.5.

@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 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
 
  • Like
Reactions: ChrisCharman
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.