After review, we have documented a number of sub-systems and utilities that cannot be built on Windows using the MinGW/MSYS environment:
- amshello - uses fork which doesn't exist for mingw
- bpstats2 - uses SIGUSR1 which doesn't exist for mingw
- bpchat - builds but test does not pass - not building
- bpcp - relies on waitpid, kill, WIFEXITED, and WEXITSTATUS
- bpcpd - daemon for bpcp so doesn't make sense to build if bpcp doesn't
- owlttb - needs SIGPIPE which windows does not support
We should determine how to proceed - are any of these functions critical? Or do we simply document that they are not available on Windows?
Anonymous
I would say none of them are critical, though bpchat and bpcp and bpcpd are important enough to address in the 3.6.3 release. For 3.6.2 we should just document - in the release notes and in the man pages - that all of these programs are not available on Windows. (For any of them that are missing man pages, let's also aim to write man pages for the 3.6.3 release.)
When documenting the absence of these executables on Windows, let's note that we also need man pages for bpstats2 and bpchat.
bpchat is now built on Windows. The test relies on mkfifo which does not exist in mingw but bpchat itself does work.
Man pages now also exist for bpstats2 and bpchat.