I should try and reproduce in one my my old OS VMs the error I saw in the buildbots with the above. From there we can decide what needs to be done. I actually think gcc{6,7,8,9} are all fine with isl 0.21, and the errors I saw in the buildbots that forced me to revert my recent attempt at updating isl was a combination of the above and the interesting Xcode 10.2 specific issue in https://trac.macports.org/ticket/58260. Note we anyway should hold off updating in any way the gcc ports until the Xcode issue is fixed, as otherwise we will break things badly on macOS10.14 (at the moment, users should be OK in that they can use the existing binary tarballs).
This comment has been minimized.
this might have set up a circular dependency loop on some systems, as gcc6 both needs it and is required to build it.
This comment has been minimized.
Yes, I think that might well explain what I saw....
This comment has been minimized.
(cc'ing @MarcusCalhoun-Lopez )
I should try and reproduce in one my my old OS VMs the error I saw in the buildbots with the above. From there we can decide what needs to be done. I actually think gcc{6,7,8,9} are all fine with isl 0.21, and the errors I saw in the buildbots that forced me to revert my recent attempt at updating isl was a combination of the above and the interesting Xcode 10.2 specific issue in https://trac.macports.org/ticket/58260. Note we anyway should hold off updating in any way the gcc ports until the Xcode issue is fixed, as otherwise we will break things badly on macOS10.14 (at the moment, users should be OK in that they can use the existing binary tarballs).