@zbeekman. It's an easy fix. I can push a new commit or you can just replace the text
./build flex --default --query-versionwith the text
./build.sh -V flex
@rouson I'm second guessing myself regarding some CAF semantics. Can you please confirm that there is no synchronization needed between the following two statements:
b(:) = a(:)[me+1]
matches = all( a_local(:) == b(:) )i.e., the local image won't proceed until the assignment on line one completes
brew update
brew install --cc=gcc-6 OpenCoarrays # to get gcc to build the library... should also build fine with clang
Dear @zbeekman @rouson I have a problem with your great install.sh script. I am pushing my bosses to adopt opencoarrays, but they are strongly addicted to CentOS, and they are essentially paranoiac (root installation is not viable). The big issue is to install a recent gcc. Indeed, we have manually compiled installed gcc 6.2, but we have problem with gcc 6.3, thus I tried to exploit you script (that I used every week to update my local gcc-developing-trunk). However, I was not able to understand how to set the installer to point to 6.3 trunk instead of 6.1 (the default one). The syntax I use for the developing trunk is:
/install.sh -p gcc -b trunk -i /opt/gcc/bin/7.0.0Can you let me know how to execute the script for installing 6.3 trunk?
Thank you very much for help!
Cheers
@rouson
Dear Damian,
BTW, there exists a such a broad range of users: some refuse to use anything but a static Makefile; others prefer to use CMake; others use package management; others exclusively use the bash installation script install.sh
:smile: I know. My bosses refuse all but CentOS... it is really a nightmare, not only for Fortran just think to LaTeX: using recent LaTeX packages, namely less old than 10 years becomes quickly a problem :smile:
Currently my workflow is strongly based on OpenCoarrays:
- I use OpenCoarrays for CAF projects (mainly HASTY);
- I use OpenCoarrays script to install (weekly/monthly) the latest gcc trunk for all Fortran projects;
- I use Zaak's docker image for gcc nightly build (occasionally to check if some compiler's issues evolves);
- now I will use OpenCoarrays script to install the latest gcc stable on my bosses' workstation :smile:
Thank you very much for the help, you rocks!
P.S. could you be interest on a very abstract designing of Fortran CFD libraries? I recently made important steps toward a really abstract CFD code exploiting many abstract libraries (obviously into which is FOODIE, FOODIE paper will be completed soon...)
Dear Damian ( @rouson @zbeekman ), as usual, today I tried your script to install the latest gcc 7.1 , but when I tried to list the available branches I got
┌╼ stefano@zaghi(09:56 AM Wed May 03) on master
├───╼ /opt/opencoarrays 20 files, 224Kb
└──────╼ ./install.sh --list-branches gcc
/opt/opencoarrays/prerequisites/build-functions/set_or_print_url.sh: line 49: version_to_build: unbound variableIs this an issue of my env?
Is there an alternative to list available releases instead of branches?
I tried the following without success
╼ stefano@zaghi(09:58 AM Wed May 03) on master
├───╼ /opt/opencoarrays 20 files, 224Kb
└──────╼ ./install.sh -p gcc -I 7.1 -i /opt/arch/gcc/bin/7.1 -j 8
...
opt/opencoarrays/prerequisites/downloads /opt/opencoarrays
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0
curl: (9) Server denied you to change to the given directory
2017-05-03 07:58:52 UTC [ info] Cleaning up. Done
2017-05-03 07:58:52 UTC [ info] Cleaning up. DoneCheers
Hi @szaghi. I don't know how easy it would be to list the available releases. Requesting the list of branches results in the issuance of the command "svn ls svn://gcc.gnu.org/svn/gcc/branches/". By contrast, releases are downloaded from an ftp server that is accessed via curl, wget, or ftp (in order from most preferred to least preferred). In order to list releases, I would have to sort out how to list the files in a particular directory of the ftp server using each of the aforementioned three methods. I recommend using the command "./install.sh -U gcc" to list the default URL for downloading GCC (or replace GCC with the name of any other package that the installer knows how to build). Once you have that URL, you can visit the server in a browser to see the available packages.
With all the said, seeing the list will be of limited value if you're planning to use the compiler with OpenCoarrays. For several years to come (certainly at least 2-3), it will always be advisable to use OpenCoarrays with the latest GCC release. Until recently, that meant using 6.3.0. However, GCC 7.1.0 was released about a month ago as you probably know and just yesterday @zbeekman released OpenCoarrays 1.9.0 with experimental support for some exciting new features for users of GCC 7.1.0. Zaak or I will explain more in an email to the OpenCoararys mailing list sometime within the next 24 hours so watch for that if you're on the OpenCoararys Google Group mailing list.