[ML] Upgrade the compiler used on Linux #2
Conversation
We have already upgraded the macOS and Windows compilers on the master branch. This change upgrades the Linux compiler. The new compiler is gcc 7.3, upgraded from gcc 6.2. The OS used to build releases is also upgraded, to CentOS 6 from Fedora 10. gcc 7.3 is built from source with the --enable-vtable-verify option so that the -fvtable-verify=std option could possibly be used in the future. Finally, the -std flag has been changed to allow C++14 features to be used. This matches macOS and Windows. However, for ease of backporting it is best that we don't use C++14 features until version 6.x is nearing end-of-life.
|
When this is merged the Jenkins slave for the master branch will need to be swapped. The new CentOS 6 slave is ready to go and I tested that it works on this branch in my fork. I'll wait for @hendrikmuhs to update his Linux machine before merging this. |
build-setup/linux.md
Outdated
| @@ -48,22 +48,27 @@ The `CXX` environment variable only needs to be set when building tools on Linux | |||
|
|
|||
| We have to build on old Linux versions to enable our software to run on the older versions of Linux that users have. However, this means the default compiler on our Linux build servers is also very old. To enable use of more modern C++ features, we use the default compiler to build a newer version of gcc and then use that to build all our other dependencies. | |||
|
|
|||
| Download `gcc-6.2.0.tar.bz2` from <http://ftpmirror.gnu.org/gcc/gcc-6.2.0/gcc-6.2.0.tar.bz2>. | |||
| Download `gcc-7.3.0.tar.bz2` from <http://ftpmirror.gnu.org/gcc/gcc-7.3.0/gcc-7.3.0.tar.bz2>. | |||
There was a problem hiding this comment.
link does not work for me, looks like they removed bz2 archives.
There was a problem hiding this comment.
Thanks. I changed it to the .gz one instead.
(I also removed a reference to YaST in the same file, as I think nobody uses that any more.)
(Also removed a reference to YaST)
|
the link for apr is broken as well, they upped the version to 1.5.3, just changing the version should work. |
|
sorry, wrong button |
|
I changed the APR download links to match what we use in the Docker setup (which is what we ship). |
|
I worked through it. For some reasons I had some problems with builtin expat of apr utils. I succeeded to compile it using the system expat. This should work, if not I will further investigate. As a final suggestion: After compiling gcc, it should be mentioned that you have to switch to the environment mentioned in the very beginning. Otherwise you (I did) easily forget when working through this document. |
|
Thanks @hendrikmuhs. I pushed another commit that adds a note about reseting As for using the built in expat of APR utils, it built fine with the built in expat in our Docker container and on our Jenkins build VMs. For a personal development laptop it really doesn't matter either way. It's probably not worth putting any effort into finding out what the problem was unless it starts to affect many people. |
sophiec20
changed the title
We have already upgraded the macOS and Windows compilers on the master branch. This change upgrades the Linux compiler. The new compiler is gcc 7.3, upgraded from gcc 6.2. The OS used to build releases is also upgraded, to CentOS 6 from Fedora 10. gcc 7.3 is built from source with the --enable-vtable-verify option so that the -fvtable-verify=std option could possibly be used in the future. Finally, the -std flag has been changed to allow C++14 features to be used. This matches macOS and Windows. However, for ease of backporting it is best that we don't use C++14 features until version 6.x is nearing end-of-life.
We have already upgraded the macOS and Windows compilers on the master
branch. This change upgrades the Linux compiler.
The new compiler is gcc 7.3, upgraded from gcc 6.2. The OS used to
build releases is also upgraded, to CentOS 6 from Fedora 10.
gcc 7.3 is built from source with the --enable-vtable-verify option so
that the -fvtable-verify=std option could possibly be used in the future.
Finally, the -std flag has been changed to allow C++14 features to be
used. This matches macOS and Windows. However, for ease of backporting
it is best that we don't use C++14 features until version 6.x is nearing
end-of-life.