[MacPorts] #64026: JAGS requires GCC11 which fails to build on PowerPC [solved]

MacPorts noreply at macports.org
Sun Dec 12 23:16:38 UTC 2021


#64026: JAGS requires GCC11 which fails to build on PowerPC [solved]
---------------------------+---------------------
  Reporter:  barracuda156  |      Owner:  (none)
      Type:  defect        |     Status:  new
  Priority:  Low           |  Milestone:
 Component:  ports         |    Version:  2.7.1
Resolution:                |   Keywords:  powerpc
      Port:  jags          |
---------------------------+---------------------

Comment (by barracuda156):

 Replying to [comment:7 kencu]:
 > You seem to often have ports asking for gcc11 on your 10.5 PowerPC
 system. That should never happen!
 >
 > MacPorts has been set up to only use up to gcc7 on systems < 10.6
 SnowLeopard.  It should never ask for gcc11 on such systems. If it does,
 there is some serious mixup somewhere happening.
 >
 > Please check and make certain that there are no places in your PowerPC
 10.5 installation where you might have modified something to change
 MacPorts default of only using gcc7 or less.
 >
 > (Now on systems >= 10.6, then MacPorts is set up to use gcc11. So on
 PowerPC 10.6, which we try not to talk about too much here for fear of
 getting everyone irate, you will get this screwball request for gcc11
 sometimes as MacPorts is set up to use gcc11 on >= 10.6, so that needs to
 be fixed here and there. But you should never see this on PowerPC 10.5).

 Yes, this JAGS issue can be ignored, it does not arise with default config
 on 10.5.8. I forgot to update it earlier, and now updated it with "solved"
 just in order to make sure no one tries to fix anything, as no fixes
 needed.

 However tbb problem, when it asked for clang-7 on 10.5.8 PPC (as well as
 on 10.6 PPC) is a genuine problem occurring with completely clean Macports
 config on 10.5.8: https://trac.macports.org/ticket/64027 (you know it, but
 I leave the link for others' ref).

 At the moment I have set up 10.5.8 with Macports with no changes to config
 of the latter (on 10.6 PPC I have used your set up as the base, but added
 several custom Portfiles that make failing ports built successfully:
 indeed your examples proved very helpful and work in most cases).

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


More information about the macports-tickets mailing list