[MacPorts] #56922: Libgcc7 @7.3.0_1 fails to build on PPC Tiger, Mac OS X 10.4.11, because comparison of stages 2 and 3 fails

[MacPorts]

#56922: Libgcc7 @7.3.0_1 fails to build on PPC Tiger, Mac OS X 10.4.11, because
comparison of stages 2 and 3 fails
-------------------------+--------------------
  Reporter:  ballapete   |      Owner:  (none)
      Type:  defect      |     Status:  closed
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.5.3
Resolution:  worksforme  |   Keywords:  tiger
      Port:  libgcc7     |
-------------------------+--------------------

Comment (by leavenode):

 I've pretty much decided to get too hung up on using these old machines
 for web browsing as that seems a losing battle now, the way the web is
 advancing. Nice to have some web capability though, so I should look at
 building TFF at some point. A good exercise for it's own sake.

 And of course always possible to X-forward a browser window from one of my
 Linux boxes, and then there are the web rendering proxies which I haven't
 really looked at yet.

 But if I want to download a file onto one of my G4s, most often I just ssh
 in and wget the file. wget is so much more reliable anyway.


 Replying to [comment:85 kencu]:
 > I have been building TenFourFox since 2018. One of the other regulars
 around here, Riccardo, and I sorted out the patches to make it build as
 Intel on a Tiger i386 machine over the Christmas holidays back then. I
 find it is very simple to build, but takes time.
 >
 > I wrote up a Portfile to automatically build it for MacPorts
 <https://github.com/kencu/tenfourfox-macports>, but -- it was a big huge 6
 hour build and in the end I just built it every time there was a new
 version and uploaded it to the TenFourFox sourceforge repo.
 >
 > Here's how I build it on Intel from their default github repo:
 >
 > <https://github.com/kencu/tenfourfox/blob/FPR32branch/HOWTOBUILD>
 >
 > Building it on 10.5 PPC is a bit easier because you don't need clang-3.4
 and yasm, or any patches.
 >
 > I didn't know about that thread you referenced. Perhaps I will answer
 some of the questions in there. I use gcc7/libgc7 7.4.0 still because gcc7
 7.5.0 introduced a new bug that makes a lot of software crash. It's a bit
 technical to explain but it has to do with an interaction between the
 system libstdc++ and the one installed by libgcc 7.5.0. Upstream thinks
 they have a fix for this that might work.
 >

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