[MacPorts] #54124: guile @2.2.2 won't build on PPC Leopard, Mac OS X 10.5.8, because is uses non-existing /lib/cpp as C preprocessor

[MacPorts]

#54124: guile @2.2.2 won't build on PPC Leopard, Mac OS X 10.5.8, because is uses
non-existing /lib/cpp as C preprocessor
------------------------+---------------------------------------
  Reporter:  ballapete  |      Owner:
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.4.1
Resolution:             |   Keywords:  tiger leopard snowleopard
      Port:  guile      |
------------------------+---------------------------------------

Comment (by kencu):

 Replying to [comment:11 ballapete]:
 > Replying to [comment:10 kencu]:
 > > BTW, you know how to "peg" a port at a certain version, so it won't
 update?
 > > If you need to know how to do this, let me know.
 >
 > Yes, to know this would probably fine! (I am changing the Portfiles so
 that they do not show a new version.)

 Homebrew has automated this with a `peg` command. On Macports, you do it
 manually, but with more control.

 The trick is to use a local repository of Portfiles that you maintain
 yourself, separate from the frequently-updated MacPorts ports
 distribution. <https://guide.macports.org/chunked/development.local-
 repositories.html>

 You have your macports installation look first in your local repository
 for portfiles by putting your repo ahead of the macports repo in
 `sources.conf`. If it finds your Portfile for a port, it stops looking
 further and never finds the newer, incompatible current macports version.

 There are two reasons I put ports in my local repo:
 1. They are huge, and I don't want to update them all the time.
 2. Newer versions are broken, and I need to stick with the last working
 version.

 If you find ports that you don't want to update all the time (like gcc6,
 or clang, or other huge ports that there is no reason to update frequently
 on 10.4 and 10.5, you can move the ports in there (the whole port folder,
 with the macports structure of folders above it).

 See <https://github.com/kencu/TigerPorts> ,
 <https://github.com/kencu/LeopardPorts>, and
 <https://github.com/kencu/SnowLeopardPorts> for mine. You can use my repos
 as a start if you want, or just build your own. Sooner or later, repos
 like the ones I've started will be needed for all users of Tiger / Leopard
 / SnowLeopard, so that's why I started them last year.

 Now if you have run `sudo port selfupdate` and found yourself with a port
 that won't build, you will need to go backwards in time to get the last
 version of that Portfile that you installed that did work, and put that
 port in your local repo until it gets fixed, if it ever does.

 One tested way of going back in time using github is here :
 <https://lists.macports.org/pipermail/macports-
 dev/2016-December/035058.html>. There is an old page about how to do this
 from the `svn` era that is not too useful anymore after the change to
 github <https://trac.macports.org/wiki/howto/InstallingOlderPort>.

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