Setting up Linux environment as a testbed for compilation commands

To build the Numpy C files, I need to get some documentation on C and C++ – but this is missing on the VSI site. Asked Brett, got that – plus what he had done on this in his spare time: He installed the bunch on a Windows PC running Cygwin, started a build (in C only) and trapped the output in a file; so he could transfer that into a plain, straightforward DCL procedure that compiled it all, placed modules in a library, and created the shared image. He passed it all in a backup file on the CTRL-C cluster – but this has been updated to VMS OpenVMS, and my login failed – because I was denied access to two files.. Asked him to adjust….
In the mean time, this is the way to go: Build in an environment that is known to work (some way or another), pick up the output and translate that into DCL – straight-forward, without any intelligence to be gin with.
So I set up a virtual machine running CentOS 7, installed all updates which caused a bunch of issues; but finally I had a more or less stable Linux environment where I installed the packages (OpenBLAS, NumPy en SciPy) and on VMS, I installed latest versions of MMK and Make from the VMS Freeware CD’s (that I have online) – may not be the latest but for now this will do.

Had a mail from Guido: proceed with this set up: Base and additions apart, add another layer for my own changes – that means that the adapted MMS files will reside in yet another layer.