Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Clang 3.2 #114

Closed
roidrage opened this Issue Dec 15, 2012 · 3 comments

Comments

Projects
None yet
3 participants
Owner

roidrage commented Dec 15, 2012

Requested in this tweet: https://twitter.com/mavam/status/279762766573735936

Would this be doable?

Contributor

michaelklishin commented Dec 15, 2012

It is not hard for Clang and there is a PPA for GCC 4.7 but changing GCC version to a non-default one violates the principle of least surprise. A lot of stuff depends on the exact GCC version. So I am +1 for updating Clang and strongly against GCC upgrade.

mavam commented Dec 15, 2012

FIrst off, thanks for getting back to the tweet in this fashion. I'm glad that upgrading Clang works fine. I also understand your concerns about GCC 4.7. What about keeping the default to 4.6 and just installing 4.7 as separate package? Then the user can choose the compiler by setting appropriate aliases or environment variables. E.g., the compiler binary could default to gcc but another gcc-4.7 binary would exist as well. This strategy would be very valuable in the case of C++11, where every compiler release irons out a significant chunk of edges of the previous version.

Contributor

michaelklishin commented Jan 20, 2013

Clang will be updated to 3.2, GCC will not (until we migrate to the next distro release next spring)

azat added a commit to boostcache/boostcache that referenced this issue Apr 19, 2013

gildegoma added a commit to travis-ci/travis-ci.github.com that referenced this issue Aug 8, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment