Hi Stephen, Stephen Kitt wrote:
[...] > I've added tests to deactivate stack protector and relro on Windows, Good. Thanks much for that. > and more > controversially I've added x86 and x64 entries in cputable. I think that's a no-go, sorry. The problem is that after that change there is no longer one unambiguous Debian arch for each GNU triplet, which breaks - automatic determination of the Debian arch when building dpkg for a new system (less important) - "dpkg-architecture -t<triplet> -qDEB_HOST_ARCH" (very important) If the i386 cputype should behave differently for Windows arches, that could be done more directly, though the use case would have to be strong. If we want convenience synonyms for CPU types (with one being the "real" one, the rest being for user convenience), that could probably also be done, but I'm not at all convinced it would be worth the confusion. > The reason for > that is two-fold: first, the "standard" triplet for 32-bit MinGW-w64 is > i686-w64-mingw32, and lots of things break when dpkg-dev says > i486-w64-mingw32 Can you spell out this breakage with an example? Is it about the names of cross-compiler programs like i686-w64-mingw32-gcc (which could be addressed with symlinks) or something deeper? Thanks for testing, and hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
