http://bugs.winehq.org/show_bug.cgi?id=20423
--- Comment #8 from Jaime Rave jaimerave@gmail.com 2009-10-22 23:48:24 --- Hi vincent, thanks for the tip, I just run the regression test with the --disable-win16 and now the compilation error did not appear, but everything seems to work fine with that option, In fact the result was:
e8ce3e600a40a739f75d6716aae555c31b0b4d0d is first bad commit commit e8ce3e600a40a739f75d6716aae555c31b0b4d0d Author: Alexandre Julliard julliard@winehq.org Date: Fri Oct 9 18:05:57 2009 +0200
Release 1.1.31.
:100644 100644 24dd7e883474c1913fe854e73fd0eeb6dc755e59 4be71b945dcb0b679b69af9dfd4150c452288249 M ANNOUNCE :100644 100644 45a4f2a713d1d5a316ebb2159f643a2a9cb3cd74 abc6d6ab101edddab2ad87c611c7ea88d2f78e49 M VERSION :100755 100755 599d2f3bc2e3f5d4db43f96db56e5f494f2b7e54 72251ba121142c471b086b7eb35809e8625ed7f5 M configure
So looks like the problem is in one of the commits related to win16. Any other idea to get around this??