-
-
Notifications
You must be signed in to change notification settings - Fork 58
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Because the new windows-install.sh uses Ubuntu 16.04, which comes with Windows Subsystem for Linux (WSL), our Windows installer can be tested in Linux image on Travis-CI. Our release notes should indicate the following limitations: 1. The Windows installer builds the default GCC installed by apt-get, which is 5.4.0 for Ubuntu 16.04. 2. Ubuntu 16.04 comes with WSL releases 14936 or later. 3. Updating to 16.04 requires joining the Windows Insider Preview program, selecting "Fast" updates, and running do-release-upgrade.
- Loading branch information
Showing
1 changed file
with
23 additions
and
26 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
26e9991
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So to test this on Travis-CI we should be testing with Ubuntu 16.04, right? Unfortunately this will be non-trivial, since Travis provides 12.04 and 14.04 only, by default. The way to test with 16.04 would be to setup a docker image... I can do this, someday, when I have the time.
26e9991
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct. 16.04 is required because it installs GCC 5.4.0, whereas 14.04's apt-get installs GCC 4.8.
No rush. The windows-install.sh script is considerably simpler than install.sh because it is safe to assume the presence of apt-get so all prerequisites are installed with
sudo apt-get install ...
and there's no need for recursion or stack management or downloading anything directly. It's a much simpler world. :)26e9991
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rouson FYI, you can do this on most Ubuntu distros to get modern compilers:
Then
sudo apt-get install gcc gfortran g++
should get you 6.x even on 14.04. This probably works in older versions of Ubuntu as well... I'm wondering if this is worth testing. Could this possibly allow WSL builds even when the user is not in the fast-track/early release program?26e9991
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The suggested commands didn't work. The output is below. I don't think either of us should spend any more time on this without a specific user request. If a user requests an update to a newer gfortran, then we can enlist the user in assisting with finding a solution and testing it.
26e9991
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good.... without a Windows system I just thought it might be worth testing that, since it's what I normally do on older ubuntu systems.... For now I think the windows script is going to have to go untested in our CI process... Soon I hope to get shellcheck up and running, and we can throw that at it, but getting 16.04 is up and running on Travis-CI is going to be a bit time consuming.
26e9991
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also recommend against working on getting 16.04 running. It will eventually be the default on WSL. I'll mention this on comp.lang.fortran and in the LinkedIn Fortran Programmers list in case anyone can provide insights.
26e9991
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmmm... my reasoning on the last comment was erroneous (Ubuntu 16.04 becoming the default on WSL is unrelated to whether you should try to get it running in Travis-CI). Nonetheless, my conclusion would be the same: not worth the effort without a user request.