I am about to make a new xPack release with the latest commit, and I noticed
that the mingw-w64 build for Windows failed with:
/home/ilg/Work/xpack-dev-tools/openocd-xpack.git/build-assets/build/win32-x64/sources/openocd.git/src/jtag/drivers/ep93xx.c:23:10:
fatal error: sys/mman.h: No such file or directory
23 | #include <sys/mman.h>
| ^~~~~~~~~~~~
/home/ilg/Work/xpack-dev-tools/openocd-xpack.git/build-assets/build/win32-x64/sources/openocd.git/src/jtag/drivers/at91rm9200.c:15:10:
fatal error: sys/mman.h: No such file or directory
15 | #include <sys/mman.h>
| ^~~~~~~~~~~~
/home/ilg/Work/xpack-dev-tools/openocd-xpack.git/build-assets/build/win32-x64/sources/openocd.git/src/jtag/drivers/bcm2835gpio.c:20:10:
fatal error: sys/mman.h: No such file or directory
20 | #include <sys/mman.h>
| ^~~~~~~~~~~~
/home/ilg/Work/xpack-dev-tools/openocd-xpack.git/build-assets/build/win32-x64/sources/openocd.git/src/jtag/drivers/imx_gpio.c:17:10:
fatal error: sys/mman.h: No such file or directory
17 | #include <sys/mman.h>
| ^~~~~~~~~~~~
It looks like some drivers use Unix memory mapped functions that are not
available for Windows.
I added explicit `--disable-ep93xx --disable-at91rm9200 --disable-bcm2835gpio
--disable-imx_gpio` in the Windows configuration and the build passed.
If the drivers were intentionally excluded for Windows, I think that the
configure step should not allow to enable these drivers, so to prevent the
build to fail during compilation.
To be noted that in my previous release from February, the build passed with
all these drivers enabled.
Regards,
Liviu
