Hi Vasile,
Are you refering to the problem with the Linux compiler I posted?
It does not seem an easy task to do.
About the Linux compiler. I had compiled it with gcc version 9.0 due to an upgrade of my Ubuntu system which cause the issue with GLIBC. The problem was solved by recompiling it with gcc version 7. The server of Kyle should work with that version but for some
reason the new compiler is not picked up so the build (the validation of the samples and the compile of all samples) keeps failing.
I am working with Matt to move the validation, compilation and release to the server of Matt that also hosts the website since the compiler works there without a problem and it seems more logical to have it all on the same server.
In parallel I am doing the validation and compilation of all samples after a check-in on GitHub using GitHub actions. In fact it does the same validation that the server of Kyle does when you commit someting to GitHub. GitHub sends me a nice e-mail about this
validation task if it is succesfull or not , screenshot below. And since I was playing with GitHub actions I also managed to create a JAL Linux compiler and a JAL MAC compiler both only 64-bit. I also created a 64-bit Windows compiler but the strange thing
is that I cannot run it on my Windows 10 system (access denied) even when all rights are set correctly. Internet does not provide a solution for this specific problem. A complete mystery to me. For now I will still create the compilers locally but if needed
they can also be build using GitHub Actions by a press of a button (I do not create the compilers after a push to GitHub, only to be started by hand).