Check what Jean-François Piéronne states in his building procedures: Python_root:[vms]python_compiler_options.com sets the options for C, build_modules.py and build_cython_modules.py actually build the modules but also add them directoy into pythonshr.exe – I doubt this is required for these routines, there is a large number of C and Fortran sources that need to be compiled first. Numpy is the first module to build because it is a requirement for SciPy.
Also downloaded the next part requested – again an older version (2.2.4) because of the limitation to Python 2.7. Didn’t install it yet, first process NumPy and SciPy. According the building procedure, in site.py, it is required to locate them in python_root:[lib.site-packaes] :
“””Append module search paths for third-party packages to sys.path.
****************************************************************
* This module is automatically imported during initialization. *
****************************************************************In earlier versions of Python (up to 1.5a3), scripts or modules that
needed to use site-specific modules would place “import site”
somewhere near the top of their code. Because of the automatic
import, this is no longer necessary (but code that does it still
works).This will append site-specific paths to the module search path. On
Unix (including Mac OSX), it starts with sys.prefix and
sys.exec_prefix (if different) and appends
lib/python/site-packages as well as lib/site-python.
On other platforms (such as Windows), it tries each of the
prefixes directly, as well as with lib/site-packages appended. The
resulting directories, if they exist, are appended to sys.path, and
also inspected for path configuration files.A path configuration file is a file whose name has the form
.pth; its contents are additional directories (one per line)
to be added to sys.path. Non-existing directories (or
non-directories) are never added to sys.path; no directory is added to
sys.path more than once. Blank lines and lines beginning with
‘#’ are skipped. Lines starting with ‘import’ are executed.For example, suppose sys.prefix and sys.exec_prefix are set to
/usr/local and there is a directory /usr/local/lib/python2.5/site-packages
with three subdirectories, foo, bar and spam, and two path
configuration files, foo.pth and bar.pth. Assume foo.pth contains the
following:# foo package configuration
foo
bar
bletchand bar.pth contains:
# bar package configuration
barThen the following directories are added to sys.path, in this order:
/usr/local/lib/python2.5/site-packages/bar
/usr/local/lib/python2.5/site-packages/fooNote that bletch is omitted because it doesn’t exist; bar precedes foo
because bar.pth comes alphabetically before foo.pth; and spam is
omitted because it is not mentioned in either path configuration file.After these path manipulations, an attempt is made to import a module
named sitecustomize, which can perform arbitrary additional
site-specific customizations. If this import fails with an
ImportError exception, it is silently ignored.“””
So boyh Numpy and SciPy should have a .pfh file – but in neither of them such a file exists – or the need to be created.
Second: both packages seem to require ATLAS and OpenBLAS, LAPACK and BLAS are not mentioned but a solution should be possible by placing blas-routines in a library (as LAPACK already has). using the mentioned options and adjustments to the build-procedures, it should be possible to build Numpy (found info here, it also contains references to the building tools like setuptools.