This follows the same pattern as the .d files generated during compilation; the
.d files are generated as a side effect of generating the output file, and we
then include them all at build-time to register the correct dependencies. See
line 634 of driver.makefile.

This uses some general make tools, most notably "while" and "select" which come from
https://github.com/markpiffer/gmtt.git and which allow us to recursively parse the
.dep files in the given e3 installation. Broadly speaking, we start with all variables
of the form `%_DEP_VERSION` to determine the first line of dependent modules, and then
we ask them (using `fetch_deps`) what they depend on.

This seems to be a very specific, limited issue, affecting virtualbox VMs only. There appears to
be an issue with how append data is buffered and written to disk. You can see this with the
following commands:

```console
$ rm -f out.tmp && seq 1569 >> out.tmp && ls -l out.tmp
-rw-r--r-- 1 simonrose vagrant 8188 Feb 14 12:12 se.tmp
$ rm -f out.tmp && seq 1560 >> out.tmp && ls -l out.tmp
-rw-r--r-- 1 simonrose vagrant 8192 Feb 14 12:12 se.tmp
$ rm -f out.tmp && seq 9999 >> out.tmp && ls -l out.tmp
-rw-r--r-- 1 simonrose vagrant 8192 Feb 14 12:12 se.tmp
```
Note that the last two files are the same size, when they should clearly be quite different. If we
remove the `>>` and replace it with a `>`, then all works correctly:
```console
$ rm -f out.tmp && seq 9999 > out.tmp && ls -l out.tmp
-rw-r--r-- 1 simonrose vagrant 48888 Feb 14 13:14 out.tmp
```
Note the file size in this case.