Changes between Version 1 and Version 2 of Ticket #43757, comment 3
- Timestamp:
- Jul 21, 2014, 12:27:39 AM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #43757, comment 3
v1 v2 1 > To be honest, I'm not sure if there is a way around this problem, except upgrading the GCC used by the build bot from 4.2 to 4.4 (the minimum version mentioned by cppcheck), which is probably easier said then done. 1 > To be honest, I'm not sure if there is a way around this problem, except upgrading the GCC used by the build bot from 4.2 to 4.4 [[BR]] 2 > (the minimum version mentioned by cppcheck), which is probably easier said then done. 2 3 3 The `gcc-4.2` used by the buildbot is the system compiler, and Apple stopped upgrading its system gcc at version 4.2, so upgrading the system gcc to 4.4 is out of the question. Instead, the port should use `compiler.blacklist` (and/or possibly also `compiler.whitelist` and/or `compiler.fallback`) to only allow MacPorts to use compilers that work. See the UsingTheRightCompiler wiki page for more info on how to do this. Edit: turns out that that wiki page fails to mention those keywords specifically, but it still contains the same general idea that is necessary here.4 The `gcc-4.2` used by the buildbot is the system compiler, and Apple stopped upgrading its system gcc at version 4.2, so upgrading the system gcc to 4.4 is out of the question. Instead, the port should use `compiler.blacklist` (and/or possibly also `compiler.whitelist` and/or `compiler.fallback`) to only allow MacPorts to use compilers that work. See the UsingTheRightCompiler wiki page for more info on how to do this. [[BR]] Edit: turns out that that wiki page fails to mention those keywords specifically, but it still contains the same general idea that is necessary here.