After some time and a few computer changes, I've decided to give Fantom a whirl. After usual problems with Hg I managed to untangle myself and try to do bootstrap the freshest version.
Note that concurrent is not bootstrap, therefore it should be using nothing from your release dir (in your case 1.0.55 dir). But it appears that in your case that it is are using the wrong directory. If you have bootstrap built to the point where you have sys.jar and sys.pod, compiler.pod in your fantom-hg/lib directory, then just put fantom-hg/bin into your path and try rebuilding concurrent that way.
DanielFathSun 19 Sep 2010
Nvm, figured I missed a part of the documentation about substitutes.
DanielFath Sun 19 Sep 2010
After some time and a few computer changes, I've decided to give Fantom a whirl. After usual problems with Hg I managed to untangle myself and try to do bootstrap the freshest version.
Any help?
It's 32 bit Java on 64-bit Win7 (because groovy doesn't want to work with 64-bit Java).
brian Sun 19 Sep 2010
First off this is what a correct concurrent build looks like:
Note that concurrent is not bootstrap, therefore it should be using nothing from your release dir (in your case 1.0.55 dir). But it appears that in your case that it is are using the wrong directory. If you have bootstrap built to the point where you have sys.jar and sys.pod, compiler.pod in your fantom-hg/lib directory, then just put fantom-hg/bin into your path and try rebuilding concurrent that way.
DanielFath Sun 19 Sep 2010
Nvm, figured I missed a part of the documentation about substitutes.