JAGS requires GCC11 which fails to build on PowerPC [solved]

[barracuda156]

Despite I have set everywhere to use macports-gcc-7 and explicitly blacklisted later versions of gcc in port file of JAGS, it still asks to download GCC11 - which is known to fail to build on PowerPC Macs.

It is not listed in dependencies in port file, so I am out of options how to force it use gcc7 instead. Any ideas?

[ryandesign (Ryan Carsten Schmidt)]

Sounds like maybe gcc11 is a dependency of some other port that jags depends on? port rdeps jags could help you identify it.

[barracuda156]

That’s not the case. The only dependency JAGS is asking is gcc11. So there is nothing else that could possibly trigger it. Also I can confirm now that gcc11 is not needed for JAGS to compile from source, install and function. (After port install failed and no port file fixes helped, I just downloaded source code, built JAGS and installed it, with gcc7.)

[jmroot (Joshua Root)]

A log would be helpful. What the jags Portfile asks for is a compiler that supports both C++11 and fortran. At first glance it looks like gcc11 would only be considered to fulfil that request on Mac OS X 10.6 and later, but bugs are always possible.

[barracuda156]

Replying to jmroot:

A log would be helpful. What the jags Portfile asks for is a compiler that supports both C++11 and fortran. At first glance it looks like gcc11 would only be considered to fulfil that request on Mac OS X 10.6 and later, but bugs are always possible.

Problem solved, asking for jags +gcc7 made it successfully build.

[kencu (Ken)]

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).

[barracuda156]

Replying to 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).