[MacPorts] #66908: ruby30 @3.0.5_1 doesn't work properly on 10.6 ppc

[MacPorts]

#66908: ruby30 @3.0.5_1 doesn't work properly on 10.6 ppc
------------------------+---------------------------------
  Reporter:  fhgwright  |      Owner:  fhgwright
      Type:  defect     |     Status:  assigned
  Priority:  Low        |  Milestone:
 Component:  ports      |    Version:
Resolution:             |   Keywords:  snowleopard powerpc
      Port:  ruby30     |
------------------------+---------------------------------

Comment (by fhgwright):

 Replying to [comment:2 barracuda156]:
 > For the record, `ruby27` @2.7.7 fails to build:
 > {{{
 > gmake[1]: *** [ext/configure-ext.mk:174: ext/syslog/exts.mk] Abort trap
 > gmake[1]: Leaving directory
 '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_ruby27/ruby27/work/ruby-2.7.7'
 > gmake: *** [uncommon.mk:277: exts.mk] Error 2
 > gmake: *** Waiting for unfinished jobs....
 > making encs
 > gmake[1]: Entering directory
 '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_ruby27/ruby27/work/ruby-2.7.7'
 > }}}
 >
 > Not sure yet whether upstream broken something or our patches, but it
 was building before.

 Given that neither the upstream code nor the patches have changed, either
 it was flaky all along or something else changed.  You might look at what
 ports have been updated on your system since it last built successfully.

 Given that 10.6 ppc is officially unsupported, it would behoove anyone
 wanting to make that work to also have a 10.5 ppc installation for
 reference.  If something that fails with 10.6 ppc also fails with 10.5
 ppc, then that's a failure that might be reproducible by more than a
 handful of others.  If it doesn't fail with 10.5 ppc, then that provides
 an opportunity for comparative debugging.

-- 
Ticket URL: <https://trac.macports.org/ticket/66908#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS