Hi, First, no need to call me Sir; Jaap is fine :-) On 14/01/18 09:34, Andrew Jauhari wrote:
Hello Sir,
Regarding to this matter where you give this step by step :
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Just installing the package above is not enough. What you need to do is to install the package _inside_ the chroot. The steps you need to take are (roughly, it may vary slightly depending on your environment):
- copy icpc-kotlinc_1.1.4-3~icpc_all.deb somewhere into your chroot - enter the chroot: sudo chroot /chroot/domjudge (or whatever path you build it at) - install the package there: dpkg -i /path/to/icpc-kotlinc_1.1.4-3~icpc_all.deb - if dpkg complains about missing dependencies, run 'apt-get -f install' or install them and then try again - exit the chroot and test if it works
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
It works well. Now Kotlin is work in our Domjudge. It think it should be added to installation manual at Domjudge page
I'll have a look at creating a small script that makes the above a bit easier, and documenting chroot operations a bit more.
Thanks for your guidance Sir, it is so helpful. :)
P.S. On second thought, do you mind answer my latest mail question about re-run chroot, Sir ?
See below.
Regards,
Andrew Jauhari
On 1/14/2018 12:18 AM, Andrew Jauhari wrote:
I will try them tomorrow since I'm not at my office anymore, I will update you about this whether it works or not.
But lastly I want to ask about this,
Do re-running dj_make_chroot and dj_make_chroot_java for second times will affect the whole domjudge especially judgehost? I asked this because when I suspect about kotlin is not included in chroot enviroment, i tried to re-run them. The judgehost itself seems works after that. But I dont know the impact it will create. Can you give confirmation and more information about this ?
If you rerun dj_make_chroot, then you're creating the chroot from scratch, so any changes you made there before are lost. That also means that you'd have to rerun dj_make_ubuntu_java_chroot.
And if it has impact to domjudge, please tell me too if I need to reconfigure the whole judgehost from the scratch. The judgedaemon itself does not modify the chroot at all, it only read-only bind mounts parts of it during each judging (see judge/chroot-start-stop.sh). Thus you can safely rebuild or change the chroot while the judgedaemon is not running.
Best, Jaap
Thanks again, Sir
Regards Andrew Jauhari