Menu
▾
▴
#246 swak4Foam will not build with foam-extend 4.0's AllMake.stage5 script due to missing revision name
new
None
high
major
Always
none
other
2019-04-25
2019-04-23
No
I was fully made aware of the following with the output from this post: https://www.cfd-online.com/Forums/openfoam-installation/216743-error-foam-extend-build-comilation.html#post731609
The master branch for the foam-extend-4.0 repository has in the script ThirdParty/AllMake.stage5 the following lines:
SWAK_RELEASE_VERSION=0.4.0 hg checkout version_${SWAK_RELEASE_VERSION}_v2.x
At first this may look innocent, but the branch/revision version_0.4.0_v2.x does not exist in the Mercurial repo for swak4Foam.
This is resulting in several people complaining on the forum that they are unable to compile swak4Foam from through foam-extend-4.0's standard installation instructions, which has resulted in at least two people on the forum getting lost in the builds and retrying several times... e.g.:
- https://www.cfd-online.com/Forums/openfoam-installation/216743-error-foam-extend-build-comilation.html
- https://www.cfd-online.com/Forums/openfoam-installation/216670-problems-compiling-foam-extend-4-0-fsifoam-ubuntu-wsl.html
As far as I can figure out, the breaking point has been for at least two people who are using Ubuntu 16.04 which provides Bison 2.7... which is why versin 0.4.2 will not build...
So, how to solve this issue? I'm not entirely certain which is the best solution, but the quickest fix would be to create the tag/branch/revision version_0.4.0_v2.x here on the Mercurial repo for swak4Foam, following the convention that was being used back then and inherited from swak4Foam's 0.3.2 and earlier versions... so that foam-extend 4.0 will still build in the next few years, at least when using the old software stack...
OK. Haven't used 4.0 for a long time (4.1 aka branch nextRelease)
I have added the tags pointing to 0.4.0, 0.4.1 and 0.4.2 and let them point to the original tags v.0.4.0 etc
Hope that fixes it
Many thanks! Yes, I've finished testing it right now and it's working as intended!
Feel free to close this report!