| 8 | 8 | a. '''Stick with ports that are known to work with the default toolchain and hope for someone to fix clang-3.7 someday.''' This is safest, but you won't be fully up-to-date with the world with every port, which may or may not matter to you. If you decide to do this, set up a local repository for ports (as I described in comment8 above). This takes 2 minutes to do. Move the older portfile for gtk3 @3.20.9_0 into there, with it's folder structure (gnome/gtk3). You are done. gtk3 will never again try to update. All other ports will move along. As you come across ports that won't update any longer, move them in there too. I have set up repositories like this for Tiger, Leopard, and SnowLeopard, and shared them on github. You can use mine if you want, or make your own. |
| 9 | 9 | b. '''Use the default toolchain for most things, but when a port like gtk3 won't update, if you need the update, try a newer gcc'''. This works, as above (comment 28). `$ sudo port -v install gtk3 configure.compiler=macports-gcc-6` will force gtk3 to install using the compiler of your choice, in this case gcc6. it will override any blacklisting in the portfile. If it builds successfully, which it does in this case, you won't know for certain if you might have a problem with c++ libraries. I believe, actually, everything will probably usually work corrrectly, but I know 0.01% of what Jeremy knows and he says you could have problems with c++ libraries doing this. Basically they could speak slightly different dialects. Some things may not interact correctly, even if they build correctly. You'll have to test them yourself. You might have problems. You might not. |
