On Fri, 12 Jan 2018 12:02:18, Brian Inglis wrote:
When the 32 bit toolchain is available under x86_64 for cross builds and testing
this doesnt make sense. at least with Mingw-w64, this is already the case: - mingw64-x86_64-gcc-core: 64-bit tools for building 64-bit EXEs - mingw64-i686-gcc-core: 64-bit tools for building 32-bit EXEs
and Windows X EoLs 32 bit? It could take a long while for US and other governments and orgs to upgrade all hardware to support 64 bit desktops.
no. the end users dont decide this, cygwin maintainers do. govt or whoever may not like it, but if the DLLs dont fit in the address space then that is the start of a losing battle. a situation which will get worse, not better. yes corinna has some creative workarounds, but its a stopgap. i say we should deprecate it now with a warning, then after a year or so officially drop 32-bit support. this doesnt stop people from using cygwin for making 32-bit EXEs as i have shown - it only stops them from running cygwin itself as 32-bit processes. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
