Re: [MacPorts] #70600: poppler requires C++20 which is not available on 10.4–10.5

[MacPorts]

#70600: poppler requires C++20 which is not available on 10.4–10.5
---------------------------+----------------------------
  Reporter:  barracuda156  |      Owner:  mascguy
      Type:  defect        |     Status:  assigned
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.10.1
Resolution:                |   Keywords:  tiger, leopard
      Port:  poppler       |
---------------------------+----------------------------

Comment (by barracuda156):

 Replying to [comment:7 mascguy]:
 > If all we need to do is fallback to a pre-C++20 version of `poppler` for
 10.5, that's (relatively) trivial. Certainly as compared to supporting a
 modern GCC on 10.5.
 >
 > Ultimately it would be easier to simply pin ports to older versions on
 10.5, when necessary.

 For poppler in particular, yes. In principle, I don’t think so: for the
 modern gcc all is needed is a few trivial changes in MacPorts setup, at
 least on 10.5 ppc/i386 (ppc64 is broken in MacPorts). That is a work for
 an hour, which has already been done anyway. Okay, another ten minutes for
 Ken to verify that he is satisfied.
 Pinning hundreds of ports is not just enormous task, it simply won’t be
 done (who is gonna do that?). To begin with, there is no way to even know
 which ports are broken on 10.5 due to archaic compiler, since there is no
 build bot and no testing. And then, testing with gcc7 is a waste of time,
 that compiler should just not be used for anything save for bootstrapping.

 On 10.6 ppc – not by virtue of the OS, but of GCC – I have more stuff
 working than on much later Intel systems.

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