Snow Leopard on Unsupported PowerPC Macs

[barracuda156]

I was curious, so I built R on 10.6 SnowLeopard Intel locally without any trouble:

$ port -v installed R
The following ports are currently installed:
R @4.1.1_0+builtin_lapack+cairo+gcc11+openmp+recommended+x11 (active) requested_variants='' platform='darwin 10' archs='x86_64' date='2021-09-06T20:49:01-0700'

and then, with that success, I logged in to the MacPorts buildbot farm and bumped the 10.6 x86_64 builder there, and it failed again with the same error as before. So -- it builds, but something I can't see locally is failing on the buildbot.

Still, encouraging for you perhaps. That's not building it on PPC of course -- who knows what might show up when you try to do that -- but it's close to what you hope for.

Thank you! I am actually getting G5 Quad now, so will try installing 10.6 first, if I pass that, I will deal with R.

 

[kencu]

I built and installed the most current R on TigerPPC after that last post with a couple of minor tweaks, so you should be able to get it running.

I left my Tiger tweaks here while I decide if they can be upstreamed:

History for math/R - kencu/TigerPorts

a local repository of ports that are configured for MacOSX Tiger and shadow newer incompatible versions of ports - History for math/R - kencu/TigerPorts

github.com

 

[barracuda156]

I built and installed the most current R on TigerPPC after that last post with a couple of minor tweaks, so you should be able to get it running.

I left my Tiger tweaks here while I decide if they can be upstreamed:

History for math/R - kencu/TigerPorts

a local repository of ports that are configured for MacOSX Tiger and shadow newer incompatible versions of ports - History for math/R - kencu/TigerPorts

github.com

Sounds great, thank you!

Could you tell me in few words, what should I change in order for it to build correctly? Sorry, I am not good with this kind of tasks

 

[B S Magnet]

Sounds great, thank you!

Could you tell me in few words, what should I change in order for it to build correctly? Sorry, I am not good with this kind of tasks

I’ll second this.

 

[barracuda156]

Just watched this on YouTube and noticed that the finder seems to be displaying correctly - mine still does not. Have i missed the fix for this?

Has anyone tried PathFinder as a replacement of a default Finder?

 

[barracuda156]

I got the Quad! Restored 10A190 image on a partition, it booted successfully.


Two questions:

– USB tethering from iPhone seems not to work. Any solution? My G5 has no Airport/BT at the moment.

– Which version of XCode should I use to try compiling stuff (and where to take it from)?

 

[B S Magnet]

I got the Quad! Restored 10A190 image on a partition, it booted successfully.


Two questions:

– USB tethering from iPhone seems not to work. Any solution? My G5 has no Airport/BT at the moment.

– Which version of XCode should I use to try compiling stuff (and where to take it from)?

I can answer these in reverse order:

The Xcode you need is the one bundled with the SL-PPC 10A96 image. It’s a specific version of Xcode 3.2 designed for working in the early Snow Leopard developer environment. Other Xcode builds won’t work.

For the former, I am going to make an educated guess, based on my applied testing of Build 10A96 components (see Table 4 in this thread’s WikiPost): either the networking-based components required for tethering from the iPhone you’re using (assuming this is an iPhone model which would have existed ca. 2008–09) were stripped out of Build 10A190 (which suffered from several components being replaced with Intel-only updates), or maybe — maybe — manually bringing in a later build of iTunes 10.6.3 (that is: manually moving components from the iTunes.pkg contents to their respective destinations on your system) and moving aside the iTunes which came bundled with Build 10A190 might help with that.

Two caveats with that reasoning: the first is I use an Android phone which, in order to USB tether to the internet, requires a community solution (which, curiously, I haven’t tried yet with my Build 10A96 test system… I might just do that soon!). The other caveat is that I’ve run nearly all of my SL-PPC testing (and all the testing info, especially in, again, Table 4, within the Build 10A96 environment, whose support for PowerPC Macs is, out-of-the-box, far more robust than Build 10A190).

Especially so, if you’re new to trying out SL-PPC, I strongly recommend that folks set up first with Build 10A96 and get a feel for the development environment which was present at that point, before trying Build 10A190.

Contrary to what might seem logical — “later” correlating with “better/more up-to-date/etc.” — SL-PPC really had its peak of functionality within a PowerPC environment with Build 10A96 (which was released around when Leopard was publicly at version 10.5.4); by Build 10A190 (around when Leopard was updated to 10.5.5 or 10.5.6), Apple’s development team on Snow Leopard had replaced hundreds of low-level frameworks, kexts, and utilities to Intel-only versions. Consequently, one of the most apparent problems when setting up Build 10A190 is its lack of AirPort support (which, according to other testers earlier in this thread, can be restored by moving in relevant components from Build 10A96 into the Build 10A190 environment). I think @ChrisCharman has had some success here, but you’ll need to check in with Chris for that.

I hope this might be somewhat helpful. Welcome to the adventure!

 

[barracuda156]

I can answer these in reverse order:

The Xcode you need is the one bundled with the SL-PPC 10A96 image. It’s a specific version of Xcode 3.2 designed for working in the early Snow Leopard developer environment. Other Xcode builds won’t work.

I hope this might be somewhat helpful. Welcome to the adventure!

Thank you!

XCode bundled with 10A190 is different, right? I just downloaded 10A190 Client and it seems to contain XCode installation. I can download 10A96, but it will take a bit of time.

 

[barracuda156]

Lastly, grab a copy of OnyX 2.2.5 (the last Snow Leopard version known to run on the PowerPC 10A96 and 10A190 builds), and under Finder, activate the “Quit Finder” option so that you can Cmd-Q on Finder when running just Geekbench. This should also help with your score.

Weirdly, I could not find it. Found 2.2.6, and it does not start.

 

[B S Magnet]

Thank you!

XCode bundled with 10A190 is different, right? I just downloaded 10A190 Client and it seems to contain XCode installation. I can download 10A96, but it will take a bit of time.

As far I know, the Xcode bundled with 10A190 Server should be the same 3.2 version found on the 10A96 Server image. As I look at the mpkg for it, I can see the touch data is October 12th, which is in keeping with when Build 10A190 was assembled, but otherwise it should be identical as what came bundled in June 2008 with 10A96.

Weirdly, I could not find it. Found 2.2.6, and it does not start.

Thanks for noting that. I added a link to the WikiPost on where to get 2.2.5. Here’s the source post in this discussion. Per @ojfd , just follow the download icons on each page.

Although I’ve tried to be thorough and descriptive in the WikiPost for this project, I know there are things buried within this 1,100-plus post thread which have not been indexed or referenced in the WikiPost. Fortunately, searching within the thread is doable, and you’ll be able to see whether questions you may have were discussed previously.

 

[barracuda156]

After that, things are close to working for simpler ports (the ones that use the built in compilers in /usr/), but there was one more hiccup to fix before the downloads would work correctly. The sandboxing code is slightly different between Leopard and SnowLeopard, and on PPC SnowLeopard, we have to use the older Leopard version. I did that like this:

$ diff -u /opt/local/libexec/macports/lib/port1.0/portsandbox.tcl.orig /opt/local/libexec/macports/lib/port1.0/portsandbox.tcl
--- /opt/local/libexec/macports/lib/port1.0/portsandbox.tcl.orig    2021-09-01 15:47:07.000000000 -0700
+++ /opt/local/libexec/macports/lib/port1.0/portsandbox.tcl    2021-08-29 19:33:28.000000000 -0700
@@ -121,7 +121,7 @@
     foreach dir $allow_dirs {
         foreach perm $perms {
             append portsandbox_profile " (allow $perm ("
-            if {${os.major} > 9} {
+            if {${os.major} > 10} {
                 append portsandbox_profile "subpath \"${dir}\"))"
             } else {
                 append portsandbox_profile "regex #\"^${dir}/\"))"

at that point, MacPorts began working correctly. You THEN run "sudo port -v sync" and MacPorts will update it's local copy of all the Portfiles, and then iterate through each one, generating an index of what is happening in the Portfiles. If you run "sudo port -v sync" before you make the architecture changes above, then the PortFiles can be parsed incorrectly (following the default code paths for Intel on SnowLeopard instead of code paths for PPC). So it is best if you generate this Index AFTER you have updated your macports.conf.

Could someone explain how to run this part? When I just copy-paste into Terminal, it does not work.

 

[joevt]

Could someone explain how to run this part? When I just copy-paste into Terminal, it does not work.

Isn't it just telling you to change the 9 to a 10 in the portsandbox.tcl file? Do it manually.

 

[ChrisCharman]

I can answer these in reverse order:

The Xcode you need is the one bundled with the SL-PPC 10A96 image. It’s a specific version of Xcode 3.2 designed for working in the early Snow Leopard developer environment. Other Xcode builds won’t work.

For the former, I am going to make an educated guess, based on my applied testing of Build 10A96 components (see Table 4 in this thread’s WikiPost): either the networking-based components required for tethering from the iPhone you’re using (assuming this is an iPhone model which would have existed ca. 2008–09) were stripped out of Build 10A190 (which suffered from several components being replaced with Intel-only updates), or maybe — maybe — manually bringing in a later build of iTunes 10.6.3 (that is: manually moving components from the iTunes.pkg contents to their respective destinations on your system) and moving aside the iTunes which came bundled with Build 10A190 might help with that.

Two caveats with that reasoning: the first is I use an Android phone which, in order to USB tether to the internet, requires a community solution (which, curiously, I haven’t tried yet with my Build 10A96 test system… I might just do that soon!). The other caveat is that I’ve run nearly all of my SL-PPC testing (and all the testing info, especially in, again, Table 4, within the Build 10A96 environment, whose support for PowerPC Macs is, out-of-the-box, far more robust than Build 10A190).

Especially so, if you’re new to trying out SL-PPC, I strongly recommend that folks set up first with Build 10A96 and get a feel for the development environment which was present at that point, before trying Build 10A190.

Contrary to what might seem logical — “later” correlating with “better/more up-to-date/etc.” — SL-PPC really had its peak of functionality within a PowerPC environment with Build 10A96 (which was released around when Leopard was publicly at version 10.5.4); by Build 10A190 (around when Leopard was updated to 10.5.5 or 10.5.6), Apple’s development team on Snow Leopard had replaced hundreds of low-level frameworks, kexts, and utilities to Intel-only versions. Consequently, one of the most apparent problems when setting up Build 10A190 is its lack of AirPort support (which, according to other testers earlier in this thread, can be restored by moving in relevant components from Build 10A96 into the Build 10A190 environment). I think @ChrisCharman has had some success here, but you’ll need to check in with Chris for that.

I hope this might be somewhat helpful. Welcome to the adventure!

Indeed wifi is working under 10A190 on both my iBook G4 and PowerBook G4 using the components from earlier builds, as detailed in the fix mentioned earlier in the thread

 

[ChrisCharman]

Has anyone tried PathFinder as a replacement of a default Finder?

I used PathFinder for a little while under 10A190 but found it frustrating. It also doesn’t remedy the disk mounting related issues which are the most prominent issues with the 10A190 Finder, as far as I’m concerned. PathFinder can be installed however if you want to give it a go.

 

[barracuda156]

I used PathFinder for a little while under 10A190 but found it frustrating. It also doesn’t remedy the disk mounting related issues which are the most prominent issues with the 10A190 Finder, as far as I’m concerned. PathFinder can be installed however if you want to give it a go.

For me 10A190 Finder doesn’t show file names unless I select a specific file, then name appears. Disks are mounting, though sometimes restart of Finder is needed. Missing names is a pain. I will try to find old PowerPC version of Pathfinder.

 

[barracuda156]

Indeed wifi is working under 10A190 on both my iBook G4 and PowerBook G4 using the components from earlier builds, as detailed in the fix mentioned earlier in the thread

For now I have been able to set up external Airport Express and connect it to Quad over ethernet. Internet works now, at the cost of not being able to use AirPlay at home.

 

[barracuda156]

I was curious, so I built R on 10.6 SnowLeopard Intel locally without any trouble:

$ port -v installed R
The following ports are currently installed:
R @4.1.1_0+builtin_lapack+cairo+gcc11+openmp+recommended+x11 (active) requested_variants='' platform='darwin 10' archs='x86_64' date='2021-09-06T20:49:01-0700'

and then, with that success, I logged in to the MacPorts buildbot farm and bumped the 10.6 x86_64 builder there, and it failed again with the same error as before. So -- it builds, but something I can't see locally is failing on the buildbot.

Still, encouraging for you perhaps. That's not building it on PPC of course -- who knows what might show up when you try to do that -- but it's close to what you hope for.

I have been half-through with Macports set up, but stuck at the last portion about gcc7 here: Sep 2, 2021
I cannot figure out how to use diff, but in earlier cases manual changes via sudo nano worked. Here I do not understand what to do.

Once Fortran compiler is set, I can try building R.

P. S. Could anyone tell me, is Macports set up from posts 1113 and 1114 is compatible with installing pkgs from posts 1111 and 1112? Or is it either/or?

 

[kencu]

If you use the built ports copied over from a 10.5 PPC system, then I suggest you don't try to build and use MacPorts on your own system as I outlined it or you will be unlikely to have much success in the short or longer term. The gcc7 in particular from 10.5 Leopard PPC has not been properly modified to work right on 10.6 PPC as per my patches, and will likely either fail to link or generate binaries that fail.

If the copied over 10.5 PPC software is all you need or want, then go ahead, as it's been built. Or copy it over from your own builds on your own 10.5 PPC system, which is quite trivial to do.

To be honest, to have any chance of happiness running 10.6 for PPC, in particular building your own software, you will have to be reasonably comfortable with things like diff and git and modifying a few Portfiles to tweak things or you will be pretty quickly miserable.

As a new user, you might consider staying on 10.4 or better 10.5 PPC, as I and others have done a lot of work over the years to make that as simple as it can currently be made for people to use, and it is a lot more tested and reliable at present than 10.6 PPC. And on 10.5 PPC, you can post tickets on MacPorts for builds that fail, like "R", and people like me will be available to fix them for you in MacPorts.

Food for thought.

 

[B S Magnet]

I have been half-through with Macports set up, but stuck at the last portion about gcc7 here: Sep 2, 2021
I cannot figure out how to use diff, but in earlier cases manual changes via sudo nano worked. Here I do not understand what to do.

Once Fortran compiler is set, I can try building R.

P. S. Could anyone tell me, is Macports set up from posts 1113 and 1114 is compatible with installing pkgs from posts 1111 and 1112? Or is it either/or?

My understanding (from trying to find a workaround myself and also dealing with kencu) is that it’s effectively an either/or situation, insofar as getting the ports you need to work on the SL-PPC system you’re running. The approach I described in posts #1111 and #1112 is what I have used and continue to use whenever I need a port whose portfile for Darwin10 isn’t intended to work on PowerPC architecture (such as the unique use-case environment of running Snow Leopard on PPC).

 

[MacPro2006VBox]

Well did you guys just recently hear about a root certificate expiring? Might want to go in and set it to always trust.

 

[B S Magnet]

Well did you guys just recently hear about a root certificate expiring? Might want to go in and set it to always trust.

The Let’s Encrypt Root Certificate expiry (using the IdentTrust DST Root CA X3) is what you’re referring to, which expired on 30 September.

I did notice it come up briefly last day with one email account I use in Leopard to retrieve mail with POP3. That email server probably needs to update its security certificate. In the meantime, I could see that approving the expired certificate manually, with the warning showing that the email server and the issuing server with the expired certificate were identical. While it’s completely possible for something like a MitM attack to occur in this situation, the email server in question is really small and doesn’t get a lot of activity.

Otherwise, with the stuff I’ve been using with the SL-PPC environment, nothing so far has broken or displayed an expired certificate error. If something does come up, I’ll be sure to post about it on here.

 

[barracuda156]

If you use the built ports copied over from a 10.5 PPC system, then I suggest you don't try to build and use MacPorts on your own system as I outlined it or you will be unlikely to have much success in the short or longer term. The gcc7 in particular from 10.5 Leopard PPC has not been properly modified to work right on 10.6 PPC as per my patches, and will likely either fail to link or generate binaries that fail.

As a new user, you might consider staying on 10.4 or better 10.5 PPC

Thank you for clarifying. I will try proceeding with building on 10.6, following your suggestions.

P. S. I have been on Macs since 2002 and ever since, my first being PowerMac G4. So I am not really a “new user”, it’s just that I never required compiling stuff from source in Terminal. I will figure it out.

 

[kencu]

Indeed, right now there is some kind of an issue with the ssl certificates that showed up and is causing havoc with a whole bunch of servers including some of the distfile servers that MacPorts uses. The fellow in charge of that is trying to straighten it out, however that is to be done.

 

[barracuda156]

If you run into any trouble, the distilled version of what you need to do is all in the readme with this repo:

GitHub - kencu/PPCSnowLeopardPorts: a local repository of MacPorts that are configured for an installation of Snow Leopard for PPC and shadow newer incompatible versions of ports

a local repository of MacPorts that are configured for an installation of Snow Leopard for PPC and shadow newer incompatible versions of ports - GitHub - kencu/PPCSnowLeopardPorts: a local reposito...

github.com

If you do run into troubles, we should be able to get you up and running pretty easily. You will certainly run into some ports that don't build and that I didn't fix in that repo (yet, at least) but the basic toolchain is intact and a lot of things did build when I tried it last.

And indeed, right now there is some kind of an issue with the ssl certificates that showed up and is causing havoc with a whole bunch of servers including some of the distfile servers that MacPorts uses. The fellow in charge of that is trying to straighten it out, however that is to be done.

Most ports have built, however I cannot go past ninja.

Here is a part of output:

:debug:configure configure phase started at Wed Oct 6 12:18:16 CST 2021
:notice:configure ---> Configuring ninja
:debug:configure Preferred compilers: gcc-4.2 llvm-gcc-4.2 gcc-4.0 macports-gcc$
:debug:configure Using compiler 'Xcode GCC 4.2'
:debug:configure Executing org.macports.configure (ninja)
:debug:configure Environment:
:debug:configure CC='/usr/bin/gcc-4.2'
:debug:configure CC_PRINT_OPTIONS='YES'
:debug:configure CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_loca$
:debug:configure CFLAGS='-pipe -Os -arch ppc'
:debug:configure CPATH='/opt/local/include'
:debug:configure CPPFLAGS='-I/opt/local/include'
:debug:configure CXX='/usr/bin/g++-4.2'
:debug:configure CXXFLAGS='-pipe -Os -arch ppc'
:debug:configure DEVELOPER_DIR='/Developer'
:debug:configure F90FLAGS='-pipe -Os -m32'
:debug:configure FCFLAGS='-pipe -Os -m32'
:debug:configure F90FLAGS='-pipe -Os -m32'
:debug:configure FCFLAGS='-pipe -Os -m32'
:debug:configure FFLAGS='-pipe -Os -m32'
:debug:configure INSTALL='/usr/bin/install -c'
:debug:configure LDFLAGS='-L/opt/local/lib -Wl,-headerpad_max_install_names -ar$
:debug:configure LIBRARY_PATH='/opt/local/lib'
:debug:configure MACOSX_DEPLOYMENT_TARGET='10.6'
:debug:configure OBJC='/usr/bin/gcc-4.2'
:debug:configure OBJCFLAGS='-pipe -Os -arch ppc'
:debug:configure OBJCXX='/usr/bin/g++-4.2'
:debug:configure OBJCXXFLAGS='-pipe -Os -arch ppc'
:debug:configure PYTHON='/usr/bin/python'
:info:configure Executing: cd "/opt/local/var/macports/build/_opt_local_var_ma$
:debug:configure system: cd "/opt/local/var/macports/build/_opt_local_var_macp$
:info:configure File "configure.py", line 91
:info:configure return b'/FS' in out
:info:configure ^
:info:configure SyntaxError: invalid syntax
:info:configure Command failed: cd "/opt/local/var/mac
info:configure SyntaxError: invalid syntax
:info:configure Command failed: cd "/opt/local/var/macports/build/_opt_local_v$
:info:configure Exit code: 1
:error:configure Failed to configure ninja: configure failure: command executio$
:debug:configure Error code: NONE
:debug:configure Backtrace: configure failure: command execution failed
:debug:configure while executing
:debug:configure "$procedure $targetname"
:error:configure See /opt/local/var/macports/logs/_opt_local_var_macports_sourc$
version:1
:debug:main Starting logging for ninja @1.10.2_1
:debug:sysinfo Mac OS X 10.6 (darwin/10.0.0d2) arch powerpc
:debug:sysinfo MacPorts 2.7.1
:debug:sysinfo Xcode 3.2
:debug:sysinfo SDK 10.6
:debug:sysinfo MACOSX_DEPLOYMENT_TARGET: 10.6
:warn:main configured user/group macports does not exist, will build as root
:debug:main Executing org.macports.main (ninja)
:debug:archivefetch archivefetch phase started at Wed Oct 6 12:31:57 CST 2021
ports/build/_opt_local_v$
debug:configure CPATH='/opt/local/include'
:debug:configure CPPFLAGS='-I/opt/local/include'
:debug:configure CXX='/usr/bin/g++-4.2'
:debug:configure CXXFLAGS='-pipe -Os -arch ppc'
:debug:configure DEVELOPER_DIR='/Developer'
:debug:configure F90FLAGS='-pipe -Os -m32'
:debug:configure FCFLAGS='-pipe -Os -m32'
:debug:configure FFLAGS='-pipe -Os -m32'
:debug:configure INSTALL='/usr/bin/install -c'
:debug:configure LDFLAGS='-L/opt/local/lib -Wl,-headerpad_max_install_names -ar$
:debug:configure LIBRARY_PATH='/opt/local/lib'
:debug:configure MACOSX_DEPLOYMENT_TARGET='10.6'
:debug:configure OBJC='/usr/bin/gcc-4.2'
:debug:configure OBJCFLAGS='-pipe -Os -arch ppc'
:debug:configure OBJCXX='/usr/bin/g++-4.2'
:debug:configure OBJCXXFLAGS='-pipe -Os -arch ppc'
:debug:configure PYTHON='/usr/bin/python'
:info:configure Executing: cd "/opt/local/var/macports/build/_opt_local_var_ma$
:debug:configure system: cd "/opt/local/var/macports/build/_opt_local_var_macp$
:error:configure Failed to configure ninja: configure failure: command executio$
:info:configure Exit code: 1
:error:configure Failed to configure ninja: configure failure: command executio$
:debug:configure Error code: NONE
:debug:configure Backtrace: configure failure: command execution failed
:debug:configure while executing
:debug:configure "$procedure $targetname"
:error:configure See /opt/local/var/macports/logs/_opt_local_var_macports_sourc$

I tried port clean and the use verbose mode:

Verifying checksums for ninja
---> Checksumming ninja-1.10.2.tar.gz
---> Extracting ninja
---> Extracting ninja-1.10.2.tar.gz
Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ninja/ninja/work" && /usr/bin/gzip -dc '/opt/local/var/macports/distfiles/ninja/ninja-1.10.2.tar.gz' | /usr/bin/gnutar --no-same-owner -xf -
---> Applying patches to ninja
---> Applying patch-configure.py-bootstrap-only.diff
Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ninja/ninja/work/ninja-1.10.2" && /usr/bin/patch -p0 < '/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/devel/ninja/files/patch-configure.py-bootstrap-only.diff'
patching file configure.py
Hunk #1 succeeded at 687 (offset 5 lines).
---> Applying patch-ninja-configure.py-remove-mmd.diff
Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ninja/ninja/work/ninja-1.10.2" && /usr/bin/patch -p0 < '/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/devel/ninja/files/patch-ninja-configure.py-remove-mmd.diff'
patching file configure.py
---> Configuring ninja
Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ninja/ninja/work/ninja-1.10.2" && /usr/bin/python configure.py --with-python=/usr/bin/python --bootstrap --verbose
File "configure.py", line 91
return b'/FS' in out
^
SyntaxError: invalid syntax
Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ninja/ninja/work/ninja-1.10.2" && /usr/bin/python configure.py --with-python=/usr/bin/python --bootstrap --verbose
Exit code: 1
Error: Failed to configure ninja: configure failure: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ninja/ninja/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a
bug.
Error: Processing of port ninja failed

Configure file has this in said place:

def msvc_needs_fs(self):
popen = subprocess.Popen(['cl', '/nologo', '/?'],
stdout=subprocess.PIPE,
stderr=subprocess.PIPE)
out, err = popen.communicate()
return b'/FS' in out

What should I try to fix that?

 

[kencu]

it is failing running some python code, trying to use the system python. If you look at the original Portfile, we see that systems < darwin 10 (snowleopard) are forced to use a newer MacPorts-provided python.

macports-ports/devel/ninja/Portfile at master · macports/macports-ports

The MacPorts ports tree. Contribute to macports/macports-ports development by creating an account on GitHub.

github.com

So here our current system has a system python that is older that the one in the final SnowLeopard 10.6.8, and is behaving like a system < darwin 10.

So you need to change the test in the Portfile to < 11 instead of < 10, so as to force the MacPorts python for this build. These are the types of fixes I put in that repo referenced.

to do a one-off fix for ninja, you edit your Portfile with:

bbedit (backtick) port file ninja (backtick)

make your edit, save the file, and then clean and retry your build.