Conversation
| version = version[0:-1].strip() | ||
| version_str = str(version) | ||
| if version_str[-1] in string.ascii_letters: | ||
| version_str = version_str[0:-1].strip() |
There was a problem hiding this comment.
| version_str = version_str[0:-1].strip() | |
| version_str = version_str[:-1].strip() |
There was a problem hiding this comment.
I'm not convinced that you really need the strip, too
There was a problem hiding this comment.
True. I don't like this workaround a lot though and I now saw that when jenkins builds gcc it uses the packages from /gpfs/bbp.cscs.ch/ssd/apps/hpc/jenkins/deploy/compilers/2020-02-01/linux-rhel7-x86_64/gcc-4.8.5/, so redeploying a different version of mpc might not be needed to deploy gcc 9.3.0. The problematic mpc installation is the one included in packages.yaml and there might be an issue just when building gcc locally
There was a problem hiding this comment.
If it's only GCC 9 that relies on mpc, then yes, it does not seem to make much sense to redeploy the one that ends up in packages.yaml, since that comes from tools/external-libraries.
This reverts commit 2e7a2c0.
3 participants
Update deployed gcc version to 9.3.0 to fix issues with gcc 9.2.0