CLion 2016.3.1 update is available

Posted on by Anastasia Kazakova

CLion 2016.3.1, the first bug-fix update for the recently released major version, is now available!

If you’re using CLion 2016.3, a patch-update should be available. If you’re using an earlier version, give CLion 2016.3 and its new features a try and download it for a free 30-day evaluation.


Download CLion 2016.3.1

Find below a short summary of the important fixes and changes:

See the full release notes here.

Your CLion Team

JetBrains
The Drive to Develop

Comments below can no longer be edited.

9 Responses to CLion 2016.3.1 update is available

  1. John says:

    December 14, 2016

    CLion 2016.3 on macOS didn’t seem to find a patch to download. Linked to the URL for the full download.

    • Anastasia Kazakova says:

      December 14, 2016

      What channel do you have in Preferences | Appearance & Behavior | System Settings | Updates? EAP or release one?

      • John says:

        December 15, 2016

        It was set to EAP. I didn’t realize that meant you wouldn’t get patches for stable. I assumed it was a superset (latest stable patches or EAP patches, whichever newer). Is that how it is supposed to work?

        Setting it back to stable worked for installing the 2016.3.1 patch, thanks.

        • Anastasia Kazakova says:

          December 15, 2016

          yes, there are no patches from EAP to stable version due to technical reasons.

  2. snek332 says:

    December 24, 2016

    First of all, keep up the good work JetBrains! Thanks for the update.

    Also, I’ve had this issue since 2016.3, and it hasn’t gone away in the last few updates, so here’s a hint to what happens.

    https://gist.github.com/anonymous/6424b9efaf5b5b8006324a4e42c00d76

    • Anastasia Kazakova says:

      December 26, 2016

      Thank you for the feedback. Not sure, we got the problem, and looks like we failed to reproduce. Do you mean you have ambiguous call reported? What’s the compiler behaviour in this case in your environment?

      • snek332 says:

        December 29, 2016

        Oh, silly of me not to mention that.

        Cygwin 2.6.0 with bundled CMake on Windows 10.

        The compiler has no problems with it, and the program behaves as expected. CLion, however, gives me a ‘Call to “pow” is ambiguous’ with a red squiggle underneath. Still persists in 2016.3.2

        • Anastasia Kazakova says:

          January 9, 2017

          We’ll check and come back to you later, thanks.

        • Dmitry Kozhevnikov says:

          January 9, 2017

          Thank you, it is indeed reproducible starting from GCC 6.2 (due to incorrect __typeof__ handling in CLion), I’ve created a ticket: https://youtrack.jetbrains.com/issue/CPP-8543

Subscribe

Subscribe for updates