Posted by
GLASS mailing list on
Nov 04, 2019; 5:59pm
URL: https://forum.world.st/Issue-260-eliminate-reliance-on-32-bit-devKitCommanLine-image-call-for-volunteers-tp5105781p5106615.html
On 11/1/19 3:50 PM, BrunoBB via Glass wrote:
> Dale,
>
> Tracking the errors (at least in my installation) and it seems that
> $ROWAN_PROJECTS_HOME is not defined.
ROWAN_PROJECTS_HOME is supposed to be added to the custom_stone.env file
in the install_launcher.st script[1], called on this line[2] in the
bootstrap_launcher script -- there is stop/start netldi following that
to ensure that ROWAN_PROJECTS_HOME gets set for all topaz sessions
launched against that stone ...
Could you have somehow bypassed that step?
I think that if you want to install in a freshly cloned GsDevKit_home
instance, you should just skip the initial `updateGsDevKit -gdtcs` and
then you'd be fine after that ...
I ran my tests in a separate GsDevKit_home instance (not freshly cloned,
so the devKitCommandLine image had already been defined ... just
invoking `devKitCommandLine` in a fresh clone, should build the
devKitCommandLine image) and every time I ran into an error I would
checkout the master version delete the shared/gemstone directory, fix my
scripts (in another close) push to issue_260 and then do a fresh
checkout and pull and then run the scripts from the beginning ...
You should not have to edit scripts and hardcode paths...
[1]
https://github.com/GsDevKit/GsDevKit_home/blob/issue_260/shared/repos/GsDevKit_launcher/rowan/tonel/gsdevkit_launcher-Scripts/GdkL_Install_Launcher.class.st#L128-L152[2]
https://github.com/GsDevKit/GsDevKit_home/blob/issue_260/alt_bin/bootstrap_launcher#L47
>
> Because i change that variable in some scripts with hardcoded path and i was
> able to go further but eventually failed at:
> /home/gemstone/GsDevKit_home/shared/repos/GsDevKit_launcher/bootstrapping/gemstone/bin/bootstrap_install_tode.tpz
>
> Because /usr/local/bin/smalltalk/gemstone/topaz does not exist, the actual
> error:
>
> /home/gemstone/GsDevKit_home/shared/repos/GsDevKit_launcher/bootstrapping/gemstone/gsdevkit_home/newBuild_SystemUser_gsdevkit_launcher_tode:
> /home/gemstone/GsDevKit_home/shared/repos/GsDevKit_launcher/bootstrapping/gemstone/bin/bootstrap_install_tode.tpz:
> /usr/local/bin/smalltalk/gemstone/topaz: bad interpreter: No such file or
> directory
This error is also a result of not running the install_launcher.st
script[1] ... you are missing symbolic links that are created here[3].
Perhaps you should try to install in a fresh clone and skip the
`updateGsDevKit -gdtcs` step?
Dale
[3]
https://github.com/GsDevKit/GsDevKit_home/blob/issue_260/shared/repos/GsDevKit_launcher/rowan/tonel/gsdevkit_launcher-Scripts/GdkL_Install_Launcher.class.st#L156-L169_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass