Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop support for Ubuntu Raring (13.04) #1924

Closed
AtnNn opened this issue Jan 30, 2014 · 9 comments
Closed

Drop support for Ubuntu Raring (13.04) #1924

AtnNn opened this issue Jan 30, 2014 · 9 comments
Assignees
Milestone

Comments

@AtnNn
Copy link
Member

AtnNn commented Jan 30, 2014

Ubuntu Raring has reached its end of life and is no longer supported by launchpad:

https://wiki.ubuntu.com/Releases

The oldest version of Ubuntu that is still supported by Canonical is Lucid (10.04 LTS). It will be supported until April 2015.

@ghost ghost assigned AtnNn Jan 30, 2014
@AtnNn
Copy link
Member Author

AtnNn commented Jan 30, 2014

I have dropped support for raring in the jenkins release script.

@AtnNn AtnNn closed this as completed Jan 30, 2014
@mlucy
Copy link
Member

mlucy commented Jan 30, 2014

Does this change the set of gcc versions we have to be compatible with?

@mlucy
Copy link
Member

mlucy commented Jan 30, 2014

(In particular, are any new C++11 features now available?)

@AtnNn
Copy link
Member Author

AtnNn commented Jan 30, 2014

@mlucy no, we still need to build with GCC 4.4

If it could be a time saver, we could close #1748 by dropping support for launchpad and building the lucid packages ourselves.

@mlucy
Copy link
Member

mlucy commented Jan 30, 2014

If we could somehow make it so that we only build with versions of the STL that support rvalue references, that would be nice. (I find myself worrying right now that I'm writing code that will run super slow on 4.4, and I often choose not to use rvalue references because of that worry.) I'm not sure how worth it that is though. (@srh, do you have an opinion?)

@srh
Copy link
Contributor

srh commented Feb 12, 2014

If we could somehow make it so that we only build with versions of the STL that support rvalue references, that would be nice. (I find myself worrying right now that I'm writing code that will run super slow on 4.4, and I often choose not to use rvalue references because of that worry.) I'm not sure how worth it that is though. (@srh, do you have an opinion?)

If you're worried about 4.4, worry about 4.8. We aren't using noexcept right now, and for any type with both a copy constructor and move constructor defined, the STL will only use move operations if the move constructor (and move assignment?) are declared with noexcept.

@mlucy
Copy link
Member

mlucy commented Feb 13, 2014

So, just to be clear, what are we building with on what platforms? I.e. are we going to have to keep worrying about this indefinitely?

@AtnNn
Copy link
Member Author

AtnNn commented Feb 13, 2014

Platform Compiler
Ubuntu Lucid (10.04) GCC 4.4.3
Ubuntu Precise (12.04) GCC 4.6.3
Ubuntu Quantal (12.10) GCC 4.7.2
Ubuntu Saucy (13.10) GCC 4.8.1
Centos 6.4 GCC 4.4.7
OS X 10.7.5 Clang 3.2

@mlucy
Copy link
Member

mlucy commented Feb 13, 2014

Well, great. Should we go through and add noexcept to everything?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants